Triple
T5786802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultra Low Emission Zone |
E128286
|
entity |
| Predicate | furtherExpansionDate |
P12553
|
FINISHED |
| Object | 2023-08-29 |
—
|
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: 2023-08-29 | Statement: [Ultra Low Emission Zone, furtherExpansionDate, 2023-08-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: furtherExpansionDate Context triple: [Ultra Low Emission Zone, furtherExpansionDate, 2023-08-29]
-
A.
significantExpansionDate
Indicates the date on which an entity underwent a major or notable expansion in its size, scope, or operations.
-
B.
estimatedInitialExpansionDate
Indicates the date on which the initial expansion of something (such as a project, system, or operation) is estimated to have begun or will begin.
-
C.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
D.
plannedExtensionTo
Indicates that one entity is intended or scheduled to be extended, expanded, or continued by another entity in the future.
-
E.
expansionOpeningDate
chosen
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a1c29d48190af36cc855bb491dd |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.