Triple
T37985033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adnyamathanha |
E947664
|
entity |
| Predicate | hasTotemicLandscape |
P22129
|
FINISHED |
| Object | Flinders Ranges |
—
|
NE NERFINISHED |
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: Flinders Ranges | Statement: [Adnyamathanha, hasTotemicLandscape, Flinders Ranges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotemicLandscape Context triple: [Adnyamathanha, hasTotemicLandscape, Flinders Ranges]
-
A.
hasTotem
Indicates that one entity possesses, is symbolically represented by, or is associated with another entity as its totem.
-
B.
hasLandscapeFeatures
chosen
Indicates that an entity possesses or includes specific landscape-related characteristics or elements.
-
C.
hasWildernessCharacter
Indicates that an area possesses qualities or attributes associated with being wild, natural, and largely unaffected by human development or control.
-
D.
hasLandscapeInfluence
Indicates that one entity has shaped, altered, or significantly affected the characteristics, form, or development of a landscape.
-
E.
hasTribalPresence
Indicates that a tribal group is present, active, or represented in relation to the referenced entity or 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:20 p.m.