Triple
T33817961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rufiji people |
E866740
|
entity |
| Predicate | deltaSystem |
P177736
|
FINISHED |
| Object | Rufiji River delta mangrove system |
—
|
NE NERFINISHED |
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: Rufiji River delta mangrove system | Statement: [Rufiji people, deltaSystem, Rufiji River delta mangrove system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deltaSystem Context triple: [Rufiji people, deltaSystem, Rufiji River delta mangrove system]
-
A.
eraSystem
Indicates a temporal classification relationship where an entity is associated with a particular era or chronological system used to organize time.
-
B.
deltaType
Indicates a classification of the kind or category of change (difference) that has occurred between two related states or versions.
-
C.
deltaState
Indicates a change or transition in the state or condition of an entity between two points in time.
-
D.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
E.
delta
Indicates a change, difference, or variation between two related quantities, states, or conditions.
- F. None of above. chosen
Provenance (4 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:46 a.m.