Triple
T32575880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kegon limited express |
E832642
|
entity |
| Predicate | requiresSeatReservation |
P198941
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kegon limited express, requiresSeatReservation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSeatReservation Context triple: [Kegon limited express, requiresSeatReservation, true]
-
A.
requiresAdvanceReservation
Indicates that access to or participation in something is conditional on securing a reservation ahead of time, rather than at the moment of use.
-
B.
hasReservedSeats
Indicates that specific seats have been set aside or allocated in advance for a particular entity or purpose.
-
C.
requiresPermitOrReservation
Indicates that performing the associated activity or accessing the related resource is conditional on obtaining a permit or making a reservation in advance.
-
D.
allowsReservation
Indicates that one entity permits another entity to make or hold a reservation for its use or access.
-
E.
requiresAdvanceDiningReservation
Indicates that access to the dining experience is contingent on securing a reservation in advance.
- F. None of above. chosen
Provenance (4 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
| PDg | Predicate description generation | batch_69ff167608f08190b7cd2cf65ddecbf3 |
completed | May 9, 2026, 11:11 a.m. |
Created at: May 1, 2026, 1:04 a.m.