Triple
T34994208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Sonder |
E1009476
|
entity |
| Predicate | roleOnLarapintaTrail |
P165140
|
FINISHED |
| Object | western terminus of the Larapinta Trail |
—
|
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: western terminus of the Larapinta Trail | Statement: [Mount Sonder, roleOnLarapintaTrail, western terminus of the Larapinta Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnLarapintaTrail Context triple: [Mount Sonder, roleOnLarapintaTrail, western terminus of the Larapinta Trail]
-
A.
roleOnGR20
Indicates the specific function or position an entity holds in the context of the GR20 (e.g., within an activity, project, or system labeled GR20).
-
B.
roleOn
chosen
Indicates that an entity holds or performs a specific role or function within another entity, context, or activity.
-
C.
roleOnPern
Indicates the specific function, position, or duty an entity holds within the context of Pern.
-
D.
roleOnIsland
Indicates the specific function, position, or responsibility an entity holds within the context of an island.
-
E.
roleAtOutwild
Indicates that an entity holds or performs a specific role or position within the organization or context named Outwild.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:01 p.m.