Triple
T17556756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian railway network |
E427608
|
entity |
| Predicate | introducedHighSpeedService |
P83084
|
FINISHED |
| Object | 2000s |
—
|
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: 2000s | Statement: [Italian railway network, introducedHighSpeedService, 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedHighSpeedService Context triple: [Italian railway network, introducedHighSpeedService, 2000s]
-
A.
introducedAsHighSpeedService
chosen
Indicates that a service was launched or presented specifically as a high-speed offering.
-
B.
inauguratedHighSpeedServiceIn
Indicates that an entity began or officially launched high-speed service (such as transportation or communication) in a specified location or region.
-
C.
firstHighSpeedRailIn
Indicates that a given rail system is the earliest high-speed rail established within a specified region or country.
-
D.
hasHighSpeedLine
Indicates that there exists a high-speed rail line connection between the related entities.
-
E.
primaryHighSpeedOperator
Indicates that an entity serves as the main operator responsible for providing high-speed service or functionality to another entity.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562357b48190bde6f49df0c983c2 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.