Triple
T18279706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M561 tractor unit |
E437831
|
entity |
| Predicate | controlSystemsLocatedIn |
P33705
|
FINISHED |
| Object | driver cab |
—
|
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: driver cab | Statement: [M561 tractor unit, controlSystemsLocatedIn, driver cab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlSystemsLocatedIn Context triple: [M561 tractor unit, controlSystemsLocatedIn, driver cab]
-
A.
locationOfControl
Indicates that one entity is the place or context in which another entity exercises authority, management, or control.
-
B.
controlsLocation
Indicates that one entity has authority over, manages, or determines the status or use of a particular location.
-
C.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
D.
locationInSystem
chosen
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
E.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50054d1dc8190b31d02f617256e9d |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.