Triple
T726476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A 49 motorway |
E14735
|
entity |
| Predicate | plannedExtension |
P11869
|
FINISHED |
| Object | further south of Schwalm-Eder region |
—
|
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: further south of Schwalm-Eder region | Statement: [A 49 motorway, plannedExtension, further south of Schwalm-Eder region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedExtension Context triple: [A 49 motorway, plannedExtension, further south of Schwalm-Eder region]
-
A.
extension
chosen
Indicates that one entity is a lengthening, continuation, or added part of another entity beyond its original limits.
-
B.
missionExtension
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
-
C.
plannedUpgrade
Indicates that an entity has a scheduled or intended improvement or enhancement to be carried out in the future.
-
D.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
-
E.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f839608190878a60eb7a044ed9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.