Triple
T32447783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 168 Stairs |
E829192
|
entity |
| Predicate | monorailUse |
P174189
|
FINISHED |
| Object | assists visitors up the climb |
—
|
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: assists visitors up the climb | Statement: [168 Stairs, monorailUse, assists visitors up the climb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monorailUse Context triple: [168 Stairs, monorailUse, assists visitors up the climb]
-
A.
monorailStation
Indicates that an entity functions as a station or stop specifically for a monorail transit system.
-
B.
monorailOpeningDate
Indicates the calendar date on which a monorail system or line was first opened for public operation.
-
C.
monorailLines
Indicates that there is a monorail transit line or system associated with, serving, or present in the referenced entity.
-
D.
metro
Indicates a relationship where an entity is associated with, located in, or served by a metropolitan transit system (such as a subway or urban rail network).
-
E.
hasRailMode
Indicates that an entity is associated with or supports transportation via rail-based modes (such as trains, trams, or subways).
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e767bc8190b49fd0c4a557b464 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:56 a.m.