Triple
T16849093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jatbula Trail |
E409622
|
entity |
| Predicate | parkEntryRequirement |
P46100
|
FINISHED |
| Object | Nitmiluk National Park entry rules apply |
—
|
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: Nitmiluk National Park entry rules apply | Statement: [Jatbula Trail, parkEntryRequirement, Nitmiluk National Park entry rules apply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkEntryRequirement Context triple: [Jatbula Trail, parkEntryRequirement, Nitmiluk National Park entry rules apply]
-
A.
parkingRequirement
Indicates the specified conditions or obligations related to providing or using parking associated with an entity or activity.
-
B.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
-
C.
parkEntranceArea
Indicates the area that serves as an entrance or access point to a park.
-
D.
requiresParkTicket
chosen
Indicates that access to something is conditional on possessing a valid park ticket.
-
E.
boardingRequirement
Indicates the conditions or criteria that must be met for an entity to be allowed to board another entity (such as a vehicle, vessel, or aircraft).
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b377b5d881909f0878dd9957f3bc |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.