Triple
T16817437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris–London high-speed corridor |
E408789
|
entity |
| Predicate | openedHighSpeed1Completion |
P62160
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Paris–London high-speed corridor, openedHighSpeed1Completion, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedHighSpeed1Completion Context triple: [Paris–London high-speed corridor, openedHighSpeed1Completion, 2007]
-
A.
openedAsHighSpeed
Indicates that something was inaugurated or began operation specifically as a high-speed service or facility.
-
B.
fullOpeningCompleted
chosen
Indicates that the action or process of fully opening something has been completed.
-
C.
hasOpenedFor
Indicates that one entity has performed or appeared as the opening act or preliminary participant for another entity, typically in an event or performance context.
-
D.
openedForIND
Indicates that an entity has been opened or made available specifically for an Investigational New Drug (IND) application or process.
-
E.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e30cf48190a61936ba0a49df24 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.