Triple
T16822014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velsertunnel |
E408915
|
entity |
| Predicate | hasMaintenance |
P71131
|
FINISHED |
| Object | periodic closures for renovation and safety upgrades |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: periodic closures for renovation and safety upgrades | Statement: [Velsertunnel, hasMaintenance, periodic closures for renovation and safety upgrades]
Provenance (2 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e77ab88190be1ec8179251864e |
completed | April 18, 2026, 4:35 p.m. |
Created at: April 10, 2026, 5:23 a.m.