Triple
T9800985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A4 |
E237835
|
entity |
| Predicate | hasEuropeanRouteDesignation |
P65888
|
FINISHED |
| Object | E25 |
—
|
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: E25 | Statement: [A4, hasEuropeanRouteDesignation, E25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEuropeanRouteDesignation Context triple: [A4, hasEuropeanRouteDesignation, E25]
-
A.
hasEuropeanRoute
chosen
Indicates that a road or segment is designated as part of a specific European route within the trans-European road network.
-
B.
hasNatureDesignation
Indicates that something has been formally assigned a specific conservation, protection, or natural-area status or designation.
-
C.
isCulturalHeritageSite
Indicates that a place or structure is officially recognized and protected as having significant cultural, historical, or artistic value.
-
D.
hasHeritageDesignationRole
Indicates that an entity holds a specific role or status within a heritage designation or protection framework.
-
E.
isInHistoricCenterOf
Indicates that one entity is located within the historic center area of another entity (typically a city or town).
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda62a11a88190880e0cce24923b14 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.