Triple
T2939249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R46 subway cars |
E79343
|
entity |
| Predicate | doorsConfiguration |
P4168
|
FINISHED |
| Object | 4 pairs per side |
—
|
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: 4 pairs per side | Statement: [R46 subway cars, doorsConfiguration, 4 pairs per side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorsConfiguration Context triple: [R46 subway cars, doorsConfiguration, 4 pairs per side]
-
A.
doorConfiguration
chosen
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
B.
doorType
Indicates the specific kind or category of door associated with an entity.
-
C.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
D.
doorLocation
Indicates the spatial position or placement of a door relative to a reference structure or area.
-
E.
hasEndDoors
Indicates that an object or structure is equipped with doors located at one or more of its ends.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad986d9a248190927efc1a0c7d247f |
completed | March 8, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.