Triple
T14174902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sigatoka River |
E351305
|
entity |
| Predicate | hasSedimentTypeAtMouth |
P18668
|
FINISHED |
| Object | sand dunes |
—
|
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: sand dunes | Statement: [Sigatoka River, hasSedimentTypeAtMouth, sand dunes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSedimentTypeAtMouth Context triple: [Sigatoka River, hasSedimentTypeAtMouth, sand dunes]
-
A.
hasSedimentsThat
chosen
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
B.
hasSedimentLoad
Indicates that one entity (typically a water body or flow) carries or transports a certain amount or type of sediment associated with another entity.
-
C.
typeOfSedimentation
Indicates the specific kind or process of sediment deposition or settling that characterizes how sediment accumulates in a given context.
-
D.
hasWetlandsAtMouth
Indicates that a watercourse or water body has wetlands located at or surrounding its mouth where it meets another body of water.
-
E.
typicalSedimentSizeRange
Indicates the usual range of sediment particle sizes associated with an entity or environment.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b7cc3081909f4fa371e1eae130 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:02 a.m.