Triple
T759327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MetroAccess |
E16029
|
entity |
| Predicate | reservationWindow |
P9633
|
FINISHED |
| Object | advance booking 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: advance booking required | Statement: [MetroAccess, reservationWindow, advance booking required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservationWindow Context triple: [MetroAccess, reservationWindow, advance booking required]
-
A.
reservationSystem
Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
-
B.
modernReservation
Indicates that an entity is a contemporary or currently active reservation associated with another entity (such as a group, person, or place).
-
C.
reservationPolicy
chosen
Indicates the rules or conditions governing how reservations are made, modified, or canceled between parties.
-
D.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
E.
closedDuring
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a67f9778819098d3c144dd26b976 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.