Triple
T34876072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Railway Bridge |
E1005883
|
entity |
| Predicate | riverPreviouslyKnownAs |
P49742
|
FINISHED |
| Object | Mae Klong River |
—
|
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: Mae Klong River | Statement: [Death Railway Bridge, riverPreviouslyKnownAs, Mae Klong River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverPreviouslyKnownAs Context triple: [Death Railway Bridge, riverPreviouslyKnownAs, Mae Klong River]
-
A.
riverDivertedTo
Indicates that the natural course of a river has been intentionally redirected from its original path to a new channel or destination.
-
B.
associatedBodyOfWaterFormerName
chosen
Indicates that a body of water is linked to another name it was known by in the past.
-
C.
riverbedDivertedTo
Indicates that the natural course of a riverbed has been redirected or channeled toward another location or pathway.
-
D.
riverFormed
Indicates that a river came into existence or was created, typically as a result of natural geological or hydrological processes.
-
E.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4 p.m.