Triple
T35158311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siam |
E1015188
|
entity |
| Predicate | hasTransitInterchange |
P98214
|
FINISHED |
| Object | BTS Skytrain |
—
|
NE NERFINISHED |
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: BTS Skytrain | Statement: [Siam, hasTransitInterchange, BTS Skytrain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransitInterchange Context triple: [Siam, hasTransitInterchange, BTS Skytrain]
-
A.
hasBusInterchange
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
B.
hasInterchangeStationWith
chosen
Indicates that two transportation lines, routes, or systems share a station where passengers can transfer between them.
-
C.
hasRailInterchangeFunction
Indicates that something serves as a location or facility where rail lines connect or intersect, allowing passengers or goods to transfer between them.
-
D.
hasNearbyInterchange
Indicates that one location has a transportation interchange (such as a junction or transfer point) situated close to it.
-
E.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: May 3, 2026, 4:02 p.m.