Triple
T1338256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam–Utrecht railway |
E28404
|
entity |
| Predicate | upgrade |
P23568
|
FINISHED |
| Object | quadruple tracking between Amsterdam and Utrecht |
—
|
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: quadruple tracking between Amsterdam and Utrecht | Statement: [Amsterdam–Utrecht railway, upgrade, quadruple tracking between Amsterdam and Utrecht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgrade Context triple: [Amsterdam–Utrecht railway, upgrade, quadruple tracking between Amsterdam and Utrecht]
-
A.
upgradeType
chosen
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
B.
upgradeGoal
Indicates that an entity has a target or intended improvement to a higher level, version, or state relative to its current condition.
-
C.
upgradeProgram
Indicates that one entity improves, enhances, or replaces another entity’s program with a more advanced or updated version.
-
D.
upgradeStatus
Indicates the current state or progress of an upgrade process applied to an entity.
-
E.
upgradePath
Indicates the relationship by which one entity can be improved, enhanced, or transitioned into another, typically more advanced, version or state.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c2115d388190b031ae2de1296f8a |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.