Triple
T3347215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Cars |
E70403
|
entity |
| Predicate | controlCabLocatedIn |
P21781
|
FINISHED |
| Object | cab control cars |
—
|
LITERAL 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: cab control cars | Statement: [California Cars, controlCabLocatedIn, cab control cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlCabLocatedIn Context triple: [California Cars, controlCabLocatedIn, cab control cars]
-
A.
cabLocation
Indicates the current geographic position of a cab in space (e.g., on a map or within a defined area).
-
B.
hasControlCab
chosen
Indicates that an entity is equipped with or includes a control cab used for operating or controlling it.
-
C.
controlRoomFeature
Indicates that a feature, element, or characteristic is part of, present in, or associated with a control room.
-
D.
doorLocation
Indicates the spatial position or placement of a door relative to a reference structure or area.
-
E.
seatLocatedIn
Indicates that a seat is situated within or belongs to a specific location or area.
- F. None of above.
Provenance (3 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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb21c64448190a29631ea8f029868 |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.