Triple
T36803021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Pier (Sathorn) |
E909371
|
entity |
| Predicate | hasPierCode |
P187021
|
FINISHED |
| Object | Central Pier |
—
|
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: Central Pier | Statement: [Central Pier (Sathorn), hasPierCode, Central Pier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPierCode Context triple: [Central Pier (Sathorn), hasPierCode, Central Pier]
-
A.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
B.
hasPierName
Indicates that an entity (such as a berth, dock, or mooring location) is associated with a specific pier name.
-
C.
hasPiersOn
Indicates that one structure or location is supported or extended by piers that are physically situated on another structure or surface.
-
D.
hasPierFunction
Indicates that an entity serves the role or function of a pier, such as providing a structure that extends over water for access, docking, or related activities.
-
E.
hasPierNumberRange
Indicates that an entity is associated with a continuous range of pier numbers, from a starting pier number to an ending pier number.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.