Triple
T11458704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamilaraay people |
E271593
|
entity |
| Predicate | hasConnectionToLand |
P99675
|
FINISHED |
| Object | spiritual connection to Gamilaraay country |
—
|
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: spiritual connection to Gamilaraay country | Statement: [Gamilaraay people, hasConnectionToLand, spiritual connection to Gamilaraay country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectionToLand Context triple: [Gamilaraay people, hasConnectionToLand, spiritual connection to Gamilaraay country]
-
A.
isInLand
Indicates that one entity is located within the geographical boundaries of a land area or territory of another entity.
-
B.
hasLandComponent
Indicates that something includes, consists of, or is associated with a land-based part or portion as one of its components.
-
C.
hasLandCutOffBy
Indicates that one land area is separated or interrupted from another by an intervening feature or boundary.
-
D.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
E.
usesOnLand
Indicates that one entity employs or operates another entity specifically in a land-based context.
- F. None of above. chosen
Provenance (4 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:35 p.m.