Triple
T20664879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badtjala people |
E507857
|
entity |
| Predicate | hasTotemicBeliefs |
P94815
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Badtjala people, hasTotemicBeliefs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotemicBeliefs Context triple: [Badtjala people, hasTotemicBeliefs, yes]
-
A.
hasDreamingBeliefs
Indicates that an entity holds beliefs, views, or assumptions specifically about dreams or the nature of dreaming.
-
B.
hasDeities
Indicates that one entity possesses, is associated with, or is served by one or more deities.
-
C.
hasAnimalCult
Indicates that an entity practices or maintains a cult or organized religious veneration centered around one or more animals.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
totemicSystem
chosen
Indicates a relationship in which entities are organized or associated within a totemic system, linking them through symbolic, often clan-based or spiritual, classifications.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c2c6d48190bbfe505cf7d973f9 |
completed | April 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.