Triple
T32447785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 168 Stairs |
E829192
|
entity |
| Predicate | monorailFare |
P174479
|
FINISHED |
| Object | typically free or low-cost |
—
|
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: typically free or low-cost | Statement: [168 Stairs, monorailFare, typically free or low-cost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monorailFare Context triple: [168 Stairs, monorailFare, typically free or low-cost]
-
A.
monorailStation
Indicates that an entity functions as a station or stop specifically for a monorail transit system.
-
B.
monorailUse
Indicates that one entity makes use of, travels on, or is transported by a monorail system in relation to another entity or context.
-
C.
monorailLines
Indicates that there is a monorail transit line or system associated with, serving, or present in the referenced entity.
-
D.
monorailOpeningDate
Indicates the calendar date on which a monorail system or line was first opened for public operation.
-
E.
usesSingleFareStructure
Indicates that the same fare rules and pricing structure are applied uniformly across all relevant services or routes.
- 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_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:56 a.m.