Triple
T24159811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahakam Ulu Regency |
E598799
|
entity |
| Predicate | hasPrimaryTransportRoute |
P11026
|
FINISHED |
| Object | Mahakam 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: Mahakam River | Statement: [Mahakam Ulu Regency, hasPrimaryTransportRoute, Mahakam River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryTransportRoute Context triple: [Mahakam Ulu Regency, hasPrimaryTransportRoute, Mahakam River]
-
A.
hasTransportRoute
chosen
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
B.
hasPrimaryTransportationMode
Indicates the main or most frequently used mode of transportation associated with an entity.
-
C.
hasSecondaryTransportationMode
Indicates that an entity is associated with an additional, non-primary mode of transportation it can use or provide.
-
D.
hadTransportRoutes
Indicates that there were established transportation routes or connections between the related entities.
-
E.
hasPublicTransitRoute
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e7f8e481909c55ae66bf7b16e9 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:32 p.m.