Triple
T8518522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris–Amsterdam |
E201635
|
entity |
| Predicate | introducedAsHighSpeedService |
P83084
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Paris–Amsterdam, introducedAsHighSpeedService, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsHighSpeedService Context triple: [Paris–Amsterdam, introducedAsHighSpeedService, 1990s]
-
A.
inauguratedHighSpeedServiceIn
Indicates that an entity began or officially launched high-speed service (such as transportation or communication) in a specified location or region.
-
B.
hasHighSpeedLine
Indicates that there exists a high-speed rail line connection between the related entities.
-
C.
introducedByAmtrak
Indicates that something (such as a service, policy, feature, or change) was initiated, launched, or brought into use by Amtrak.
-
D.
primaryHighSpeedOperator
Indicates that an entity serves as the main operator responsible for providing high-speed service or functionality to another entity.
-
E.
hasUndergroundHighSpeedPlatforms
Indicates that an entity is equipped with high-speed transportation platforms located underground.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe626787c819087e72dd76b2d9310 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:16 p.m.