Triple
T22024550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A2 motorway (Netherlands) |
E543925
|
entity |
| Predicate | significantUpgradePeriod |
P106646
|
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: [A2 motorway (Netherlands), significantUpgradePeriod, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantUpgradePeriod Context triple: [A2 motorway (Netherlands), significantUpgradePeriod, 1990s]
-
A.
upgradePeriod
chosen
Indicates the time span or interval during which an upgrade is valid, active, or can be performed.
-
B.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
C.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
D.
upgradeLaunchPeriodStart
Indicates the point in time when the launch period for an upgrade begins.
-
E.
significantExpansionDate
Indicates the date on which an entity underwent a major or notable expansion in its size, scope, or operations.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ca45a08190b2d5d3a8eb37cb4b |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:23 p.m.