Triple
T2527092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | third rail (New York City area) |
E56060
|
entity |
| Predicate | mountingPosition |
P29518
|
FINISHED |
| Object | side of running rail |
—
|
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: side of running rail | Statement: [third rail (New York City area), mountingPosition, side of running rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountingPosition Context triple: [third rail (New York City area), mountingPosition, side of running rail]
-
A.
mountingLocation
chosen
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
B.
seatingPosition
Indicates the relative location or arrangement of an entity’s seat with respect to other seats or a reference point in a seating layout.
-
C.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
D.
batteryPlacement
Indicates the spatial or positional relationship specifying where a battery is located or installed relative to another object or system.
-
E.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd255f0d081908d20cfb812c4bfc1 |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.