Triple
T35881250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystery Inc. |
E1037512
|
entity |
| Predicate | hasPrimaryVehicle |
P203545
|
FINISHED |
| Object | Mystery Machine |
E922999
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Mystery Machine | Statement: [Mystery Inc., hasPrimaryVehicle, Mystery Machine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryVehicle Context triple: [Mystery Inc., hasPrimaryVehicle, Mystery Machine]
-
A.
hasPrimaryVehicularAccessTo
Indicates that one location or entity serves as the main route or means by which vehicles can reach or enter another location or entity.
-
B.
hasPrimaryDriver
Indicates that an entity is designated as the main or principal driver responsible for operating another entity, typically a vehicle.
-
C.
primaryBusinessVehicle
chosen
Indicates that one entity serves as the main or principal vehicle used for conducting the other entity’s business activities.
-
D.
hasVehicle
Indicates that one entity possesses, owns, or is assigned a vehicle.
-
E.
hasPrimaryTransportationMode
Indicates the main or most frequently used mode of transportation associated with an entity.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38a4f6c3b88190b435e6b2d1a257ce |
completed | June 22, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.