Triple
T14288819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papunya |
E354252
|
entity |
| Predicate | artStyleFeatures |
P1851
|
FINISHED |
| Object | use of traditional Dreaming stories |
—
|
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: use of traditional Dreaming stories | Statement: [Papunya, artStyleFeatures, use of traditional Dreaming stories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artStyleFeatures Context triple: [Papunya, artStyleFeatures, use of traditional Dreaming stories]
-
A.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
B.
featuresStyle
Indicates that one entity exhibits, incorporates, or is characterized by a particular style associated with another entity.
-
C.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
D.
artisticStyle
chosen
Indicates the artistic movement, style, or aesthetic approach that characterizes how something is created or visually expressed.
-
E.
notableStyleFeature
Indicates that an entity possesses a distinctive stylistic characteristic or design element that is especially noteworthy or defining.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de698023288190b1d705235c2b2ca3 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.