Triple
T37169601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silom area, Bang Rak |
E920873
|
entity |
| Predicate | BTSStationServing |
P100437
|
FINISHED |
| Object | Sala Daeng Station |
—
|
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: Sala Daeng Station | Statement: [Silom area, Bang Rak, BTSStationServing, Sala Daeng Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BTSStationServing Context triple: [Silom area, Bang Rak, BTSStationServing, Sala Daeng Station]
-
A.
servesAsThroughStationFor
Indicates that a station functions as an intermediate (through) stop for a particular service, route, or journey rather than as its starting or ending point.
-
B.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
C.
isStationOf
Indicates that a given location functions as a station (e.g., transport or service hub) associated with or serving a particular system, line, route, or organization.
-
D.
regionServedByStation
chosen
Indicates that a particular geographic region is within the service coverage area of a given station.
-
E.
stationingBasis
Indicates the underlying reason, justification, or criteria for assigning or positioning an entity at a particular location or post.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.