Triple
T12314445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1972 Stock |
E293563
|
entity |
| Predicate | doorControlLocation |
P12030
|
FINISHED |
| Object | driver and guard positions (varied over time) |
—
|
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 and guard positions (varied over time) | Statement: [1972 Stock, doorControlLocation, driver and guard positions (varied over time)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorControlLocation Context triple: [1972 Stock, doorControlLocation, driver and guard positions (varied over time)]
-
A.
doorLocation
chosen
Indicates the spatial position or placement of a door relative to a reference structure or area.
-
B.
locationOfControl
Indicates that one entity is the place or context in which another entity exercises authority, management, or control.
-
C.
controlsLocation
Indicates that one entity has authority over, manages, or determines the status or use of a particular location.
-
D.
doorLevel
Indicates the security or access level required to open or pass through a particular door.
-
E.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.