Triple
T36188512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Towuti |
E1046916
|
entity |
| Predicate | hasBasinGeology |
P46460
|
FINISHED |
| Object | ultramafic rocks |
—
|
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: ultramafic rocks | Statement: [Lake Towuti, hasBasinGeology, ultramafic rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasinGeology Context triple: [Lake Towuti, hasBasinGeology, ultramafic rocks]
-
A.
hasSedimentaryBasin
Indicates that a geological region or area contains or is associated with a sedimentary basin.
-
B.
hasGeologicalNature
Indicates that something possesses a specific geological character, composition, or formation type.
-
C.
hasWaterBasins
Indicates that one entity possesses, contains, or includes one or more water basins in relation to another entity.
-
D.
hasGeologicalUnit
chosen
Indicates that an entity is associated with or contains a specific geological unit, such as a rock layer, formation, or stratigraphic unit.
-
E.
hasGeologicalSignificance
Indicates that something possesses notable importance or relevance within a geological context, such as Earth’s structure, history, or processes.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:08 p.m.