Triple
T14058765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Alps Walking Track |
E338287
|
entity |
| Predicate | recommendedExperienceLevel |
P79458
|
FINISHED |
| Object | experienced bushwalkers |
—
|
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: experienced bushwalkers | Statement: [Australian Alps Walking Track, recommendedExperienceLevel, experienced bushwalkers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedExperienceLevel Context triple: [Australian Alps Walking Track, recommendedExperienceLevel, experienced bushwalkers]
-
A.
typicalExperienceLevel
Indicates the usual or most common level of experience associated with an entity in a given context.
-
B.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
C.
recommendedExperience
chosen
Indicates that a certain level or type of prior experience is advised or preferred for engaging in the related activity, role, or item.
-
D.
typicalSeniorityLevel
Indicates the usual or most common rank or seniority level associated with an entity in a given context.
-
E.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5686f51c81908c33143ecbaae83d |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.