Triple
T23310932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutei Basin |
E590580
|
entity |
| Predicate | basinFillThickness |
P86523
|
FINISHED |
| Object | over 10 km of sediments |
—
|
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: over 10 km of sediments | Statement: [Kutei Basin, basinFillThickness, over 10 km of sediments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basinFillThickness Context triple: [Kutei Basin, basinFillThickness, over 10 km of sediments]
-
A.
basinFill
chosen
Indicates that a basin or low-lying area becomes filled with material, such as water or sediment, as a result of accumulation over time.
-
B.
isPartOfBasinFill
Indicates that a geological unit or deposit belongs to, and was formed as part of, the sedimentary fill within a structural or depositional basin.
-
C.
basinFeature
Indicates that one entity is a physical feature or component located within or forming part of a basin.
-
D.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
E.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972acad08190bb56541b822555cd |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:06 p.m.