Triple
T18816060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wonnarua |
E460136
|
entity |
| Predicate | hasTotemicAssociations |
P116140
|
FINISHED |
| Object | local fauna of Hunter Valley |
—
|
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 fauna of Hunter Valley | Statement: [Wonnarua, hasTotemicAssociations, local fauna of Hunter Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotemicAssociations Context triple: [Wonnarua, hasTotemicAssociations, local fauna of Hunter Valley]
-
A.
hasTotem
chosen
Indicates that one entity possesses, is symbolically represented by, or is associated with another entity as its totem.
-
B.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
C.
hasTribalEntity
Indicates that one entity is associated with, belongs to, or is part of a specific tribal group or tribal organizational body.
-
D.
containsSymbioticAssociationsWith
Indicates that one entity includes or encompasses another entity with which it maintains a symbiotic (mutually dependent or beneficial) biological relationship.
-
E.
totemType
Indicates the specific category or kind of totem associated with an entity.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a3e092e081908fc310c70f646e79 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:55 a.m.