Triple
T37458031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totemic Call |
E930847
|
entity |
| Predicate | totemTribe |
P13151
|
FINISHED |
| Object | Totem |
—
|
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: Totem | Statement: [Totemic Call, totemTribe, Totem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totemTribe Context triple: [Totemic Call, totemTribe, Totem]
-
A.
totemType
Indicates the specific category or kind of totem associated with an entity.
-
B.
ethnicOrTribalBase
Indicates that something is founded on, derived from, or primarily organized around a particular ethnic or tribal group or identity.
-
C.
numberOfTribes
Indicates the total count of distinct tribes associated with a given entity or context.
-
D.
tribeOrGens
chosen
Indicates a relationship where an entity belongs to, is associated with, or is identified as a particular tribe or gens (clan/lineage group).
-
E.
totemicSystem
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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.