Triple
T32492324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paparoa Track |
E830420
|
entity |
| Predicate | bookingRequiredFor |
P105835
|
FINISHED |
| Object | huts |
—
|
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: huts | Statement: [Paparoa Track, bookingRequiredFor, huts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookingRequiredFor Context triple: [Paparoa Track, bookingRequiredFor, huts]
-
A.
bookingRequirement
Indicates that a particular condition, rule, or prerequisite must be satisfied in order to make or confirm a booking.
-
B.
bookingHubFor
Indicates that one entity serves as the central platform or system through which bookings or reservations are made for another entity.
-
C.
bookingModel
Indicates a relationship where an entity uses or is associated with a specific model or schema that defines how bookings are structured, processed, or represented.
-
D.
requiresAdvanceReservation
chosen
Indicates that access to or participation in something is conditional on securing a reservation ahead of time, rather than at the moment of use.
-
E.
agingRequirementForRiserva
Indicates that a wine must undergo a specified minimum aging period to qualify for the "Riserva" designation.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c407c3388190aa5eb09bd39022e9 |
completed | May 3, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:59 a.m.