Triple
T9776519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Routeburn Flats Campsite |
E237260
|
entity |
| Predicate | hasFee |
P68080
|
FINISHED |
| Object | camping fee required |
—
|
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: camping fee required | Statement: [Routeburn Flats Campsite, hasFee, camping fee required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFee Context triple: [Routeburn Flats Campsite, hasFee, camping fee required]
-
A.
hasCost
Indicates that one entity requires a specified amount of resources (such as money, time, or effort) to be obtained, used, or maintained by another entity.
-
B.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
C.
isFeePaying
chosen
Indicates that an entity is required to pay a fee in order to participate in, access, or receive a specified service, resource, or activity.
-
D.
containsCharge
Indicates that one entity includes, holds, or encompasses a specific charge associated with it.
-
E.
chargesMembershipFee
Indicates that an entity requires another entity to pay a membership fee in order to access its services, benefits, or participation.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda133ef548190aaecdf49de9c5aa8 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.