Triple
T36637903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Travel Information and Authorisation System |
E904509
|
entity |
| Predicate | plannedStartOfOperations |
P118154
|
FINISHED |
| Object | 2025 |
—
|
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: 2025 | Statement: [European Travel Information and Authorisation System, plannedStartOfOperations, 2025]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedStartOfOperations Context triple: [European Travel Information and Authorisation System, plannedStartOfOperations, 2025]
-
A.
plannedOpeningDate
chosen
Indicates the date on which something is scheduled or intended to begin operating or become available.
-
B.
plannedToOperateOn
Indicates that one entity intended or scheduled to perform an operation or procedure on another entity.
-
C.
plannedOperationUntil
Indicates that an operation is scheduled or intended to continue up to a specified end time or condition.
-
D.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
-
E.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:11 p.m.