Triple
T9801005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route network |
E237836
|
entity |
| Predicate | routePrefix |
P79008
|
FINISHED |
| Object | E |
—
|
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: E | Statement: [European route network, routePrefix, E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routePrefix Context triple: [European route network, routePrefix, E]
-
A.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
B.
routeExtension
Indicates that an existing route is extended beyond its original endpoint to cover additional segments or destinations.
-
C.
routeSystem
chosen
Indicates a transportation or communication network framework within which specific routes are organized, defined, or managed.
-
D.
registryPathPrefix
Indicates that one entity specifies the leading portion of a registry path under which the other entity’s registry keys or values are located.
-
E.
routeStructure
Indicates the structural or organizational relationship between a route and its constituent segments, paths, or connections.
- 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.