Triple
T3229170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barotse Floodplain |
E67694
|
entity |
| Predicate | supportsLivelihoodsOf |
P29524
|
FINISHED |
| Object | Lozi communities |
—
|
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: Lozi communities | Statement: [Barotse Floodplain, supportsLivelihoodsOf, Lozi communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLivelihoodsOf Context triple: [Barotse Floodplain, supportsLivelihoodsOf, Lozi communities]
-
A.
livelihood
chosen
Indicates that one entity serves as the primary means of support, income, or subsistence for another entity.
-
B.
supportsLife
Indicates that one entity provides conditions or resources that allow another entity to live, grow, or remain biologically viable.
-
C.
supportsCommunity
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
-
D.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
E.
supportedPopulation
Indicates that one entity provides assistance, resources, or services to sustain or benefit a specified group of people.
- 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaeb826588190a93bcfb1242310e7 |
completed | March 8, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0dc2248190a38c40f4e06cd41c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.