Triple
T17738534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batjala people |
E442788
|
entity |
| Predicate | hasTotemicRelationships |
P116140
|
FINISHED |
| Object | local land and sea country |
—
|
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: local land and sea country | Statement: [Batjala people, hasTotemicRelationships, local land and sea country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotemicRelationships Context triple: [Batjala people, hasTotemicRelationships, local land and sea country]
-
A.
hasTotem
chosen
Indicates that one entity possesses, is symbolically represented by, or is associated with another entity as its totem.
-
B.
hasRelationships
Indicates that an entity is connected to one or more other entities through specified types of relationships.
-
C.
hasRelatedTribe
Indicates that one tribe is associated or connected to another tribe in some relevant way, such as by kinship, alliance, or shared characteristics.
-
D.
totemType
Indicates the specific category or kind of totem associated with an entity.
-
E.
hasSupernaturalConnectionWith
Indicates a special, non-natural bond or interaction exists between two entities that involves supernatural forces, powers, or phenomena.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47aca27448190943c75e723ceefcc |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:09 a.m.