Triple
T20463495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grampians Peaks Trail |
E501986
|
entity |
| Predicate | sectioning |
P3120
|
FINISHED |
| Object | divided into multiple day-walk segments |
—
|
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: divided into multiple day-walk segments | Statement: [Grampians Peaks Trail, sectioning, divided into multiple day-walk segments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectioning Context triple: [Grampians Peaks Trail, sectioning, divided into multiple day-walk segments]
-
A.
section
chosen
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
B.
sectionType
Indicates the specific kind or category of section that an entity belongs to or represents.
-
C.
sectionCreated
Indicates that a new section has been created or added within a larger structure, document, or system.
-
D.
sectionIntroduced
Indicates that a particular section was introduced or added at a specific point in time or context.
-
E.
sectionProvided
Indicates that a specific section or portion of content has been supplied or made available by one entity to another.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a88374819087e7b97c83074d2c |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.