Triple
T8456958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Paris |
E199941
|
entity |
| Predicate | hasCheckInRequirement |
P27909
|
FINISHED |
| Object | advance check-in before departure |
—
|
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 check-in before departure | Statement: [London–Paris, hasCheckInRequirement, advance check-in before departure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckInRequirement Context triple: [London–Paris, hasCheckInRequirement, advance check-in before departure]
-
A.
requiresCheckIn
chosen
Indicates that one entity must perform a check-in action or be checked in as a prerequisite for another entity, event, or process to proceed.
-
B.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
C.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
D.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
-
E.
hasEntryRequirement
Indicates that one entity specifies conditions or qualifications that must be met before another entity is allowed access, participation, or admission.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe48f180c8190a71cf9d7248ade60 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.