Triple
T29973362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putra Heights |
E761377
|
entity |
| Predicate | isLRTInterchange |
P112432
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Putra Heights, isLRTInterchange, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLRTInterchange Context triple: [Putra Heights, isLRTInterchange, true]
-
A.
hasRailInterchangeFunction
chosen
Indicates that something serves as a location or facility where rail lines connect or intersect, allowing passengers or goods to transfer between them.
-
B.
hasBusInterchange
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
C.
hasDLRInterchange
Indicates that there is an interchange connection between an entity and a Docklands Light Railway (DLR) service or station.
-
D.
hasInterchangeStationWith
Indicates that two transportation lines, routes, or systems share a station where passengers can transfer between them.
-
E.
isKeyIntercityTerminalFor
Indicates that a location serves as a primary intercity transportation hub or terminal for a specified area, route, or network.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786fe3948190be625545e28e4cb7 |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:32 p.m.