Triple

T3058367
Position Surface form Disambiguated ID Type / Status
Subject Pitjantjatjara E60535 entity
Predicate connectionToLand P37306 FINISHED
Object strong spiritual connection to Uluru 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: strong spiritual connection to Uluru | Statement: [Pitjantjatjara, connectionToLand, strong spiritual connection to Uluru]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectionToLand
Context triple: [Pitjantjatjara, connectionToLand, strong spiritual connection to Uluru]
  • A. connectionTo chosen
    Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
  • B. connectsLandform
    Indicates a relationship where one landform serves as a physical link or passage between two or more other landforms.
  • C. connectedToMainlandBy
    Indicates that one landmass or area is physically linked to a mainland, typically via a bridge, causeway, or other continuous connection.
  • D. usesOnLand
    Indicates that one entity employs or operates another entity specifically in a land-based context.
  • E. connectivity
    Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
  • 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_69ad8578137c81908259dcb27c7d6d7c completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ad9e1741648190b710b7022252498d completed March 8, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69ad962326e081909d5521c3d3ea3158 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 3:02 p.m.