Triple
T23310950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutei Basin |
E590580
|
entity |
| Predicate | hasDeltaSystem |
P136580
|
FINISHED |
| Object | tidal-influenced delta |
—
|
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: tidal-influenced delta | Statement: [Kutei Basin, hasDeltaSystem, tidal-influenced delta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeltaSystem Context triple: [Kutei Basin, hasDeltaSystem, tidal-influenced delta]
-
A.
hasDelta
Indicates that there is a change, difference, or deviation between two related states, values, or versions of something.
-
B.
hasDeltaLikeFeature
chosen
Indicates that one entity possesses a characteristic or attribute that is similar to or reminiscent of a delta.
-
C.
hasDeltaType
Indicates that one entity is associated with a specific type or category of change (delta) relative to another entity or state.
-
D.
containsDelta
Indicates that one entity includes or encompasses a change, difference, or delta associated with another entity.
-
E.
hasDeltaNear
Indicates that one entity has a delta (change or difference) whose value lies within a specified proximity to another entity’s delta.
- 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.