Triple
T34114100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tjilbruke Dreaming |
E874921
|
entity |
| Predicate | explainsCreationOf |
P142943
|
FINISHED |
| Object | coastal features around Adelaide |
—
|
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: coastal features around Adelaide | Statement: [Tjilbruke Dreaming, explainsCreationOf, coastal features around Adelaide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explainsCreationOf Context triple: [Tjilbruke Dreaming, explainsCreationOf, coastal features around Adelaide]
-
A.
chroniclesCreationOf
chosen
Indicates that one entity documents or narrates the origin, development, or initial formation of another entity.
-
B.
reasonForCreation
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
C.
involvesCreationOf
Indicates that one entity brings about, produces, or results in the creation of another entity.
-
D.
createdByConstructionOf
Indicates that something comes into existence as a result of a construction process or building activity performed by an agent.
-
E.
describesOriginOf
Indicates that one entity specifies or explains the source, provenance, or origin of another 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cb777d88190a2aed1a880d4b613 |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.