Triple
T5958352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMATA 6000-series railcar |
E132571
|
entity |
| Predicate | doorSafety |
P67058
|
FINISHED |
| Object | obstruction detection |
—
|
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: obstruction detection | Statement: [WMATA 6000-series railcar, doorSafety, obstruction detection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorSafety Context triple: [WMATA 6000-series railcar, doorSafety, obstruction detection]
-
A.
gateType
Indicates the specific kind or classification of a gate associated with an entity.
-
B.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
C.
doorType
Indicates the specific kind or category of door associated with an entity.
-
D.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
E.
securityArrangementsBy
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
- F. None of above. chosen
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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03fb6bb7c81909c5629fba408dc69 |
completed | March 22, 2026, 7:15 p.m. |
Created at: March 22, 2026, 4:02 p.m.