Triple
T4289993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butchulla people |
E97364
|
entity |
| Predicate | hasCreationStories |
P11859
|
FINISHED |
| Object | stories associated with K’gari |
—
|
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: stories associated with K’gari | Statement: [Butchulla people, hasCreationStories, stories associated with K’gari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreationStories Context triple: [Butchulla people, hasCreationStories, stories associated with K’gari]
-
A.
sourceOfStories
Indicates that one entity serves as the origin or provider of stories for another entity.
-
B.
hasCosmogony
Indicates that an entity is associated with, or characterized by, a particular account or doctrine of the origin and development of the universe or cosmos.
-
C.
hasCreation
Indicates a relationship where one entity is the creator or originator of another entity.
-
D.
hasNarrative
chosen
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
E.
hasOriginStoryLocation
Indicates that an entity’s origin story takes place at or is associated with a specific location.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35061f5448190b3356b29a9129160 |
completed | March 12, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.