Triple
T3896203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palembang |
E88175
|
entity |
| Predicate | riverTransport |
P14751
|
FINISHED |
| Object | water taxis |
—
|
LITERAL FINISHED |
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: water taxis | Statement: [Palembang, riverTransport, water taxis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverTransport Context triple: [Palembang, riverTransport, water taxis]
-
A.
waterTransport
chosen
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
-
B.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
C.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
-
D.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
E.
waterwayFunction
Indicates the primary role or purpose that a waterway serves, such as transportation, irrigation, drainage, or recreation.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.