Triple
T13471110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larapinta Trail |
E311631
|
entity |
| Predicate | sectionLengthRange |
P71633
|
FINISHED |
| Object | approximately 9–31 kilometres per section |
—
|
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: approximately 9–31 kilometres per section | Statement: [Larapinta Trail, sectionLengthRange, approximately 9–31 kilometres per section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionLengthRange Context triple: [Larapinta Trail, sectionLengthRange, approximately 9–31 kilometres per section]
-
A.
typicalTrackLengthRange
chosen
Indicates the usual minimum and maximum lengths that a track associated with something tends to fall between.
-
B.
lengthRegime
Indicates a specific range or category of length within which something operates, is measured, or is classified.
-
C.
rangeSize
Indicates the extent or magnitude of the range over which something applies, varies, or is distributed.
-
D.
extensionLength
Indicates the length or magnitude of an extension from a reference point or base object.
-
E.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf22e5f88190b1078f006c8ef7c0 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.