Triple
T3466124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darug people |
E73140
|
entity |
| Predicate | hasCustomaryPractice |
P1186
|
FINISHED |
| Object | totemic clan system |
—
|
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: totemic clan system | Statement: [Darug people, hasCustomaryPractice, totemic clan system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomaryPractice Context triple: [Darug people, hasCustomaryPractice, totemic clan system]
-
A.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
B.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
C.
customaryLaw
Indicates that a relationship, behavior, or rule is governed by unwritten, traditional norms and practices recognized as binding within a community or group.
-
D.
isPracticedBy
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
-
E.
hasRiteOrTradition
chosen
Indicates that an entity is associated with, practices, or observes a particular rite, ritual, or tradition.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb0f2d3881908a5fa871341564ed |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.