Triple
T21321359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walyunga National Park |
E525622
|
entity |
| Predicate | entryFeeRequired |
P87382
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Walyunga National Park, entryFeeRequired, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryFeeRequired Context triple: [Walyunga National Park, entryFeeRequired, yes]
-
A.
feeRequirement
chosen
Indicates that a payment or fee must be provided or satisfied as a condition for a particular action, service, or relationship to occur or remain valid.
-
B.
participantRequirement
Indicates that a certain condition, qualification, or constraint must be met by an entity in order to participate in a specified activity, event, or relationship.
-
C.
registrationFee
Indicates the monetary amount required to register for a service, event, or entity.
-
D.
admissionFee
Indicates the monetary charge required for entry or participation in a place, event, or activity.
-
E.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ed1538c8190954da114e49dfa36 |
completed | April 21, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:39 p.m.