Triple
T12722883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRT Yellow Line |
E304028
|
entity |
| Predicate | hasTypicalStationType |
P47116
|
FINISHED |
| Object | underground stations |
—
|
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: underground stations | Statement: [MRT Yellow Line, hasTypicalStationType, underground stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalStationType Context triple: [MRT Yellow Line, hasTypicalStationType, underground stations]
-
A.
isOneOfMajorStationsIn
Indicates that a station belongs to the set of primary or most important stations within a specified area or system.
-
B.
isMajorStationOn
Indicates that a station serves as a primary or significant stop on a particular route or line.
-
C.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
D.
hasStationStructure
chosen
Indicates that an entity possesses or is associated with a particular station-related physical structure.
-
E.
hasStationStyle
Indicates that one entity (typically a station) possesses or is characterized by a particular architectural or design style.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:24 p.m.