Triple
T9801006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route network |
E237836
|
entity |
| Predicate | includesRouteCategory |
P13416
|
FINISHED |
| Object | main E-routes |
—
|
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: main E-routes | Statement: [European route network, includesRouteCategory, main E-routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRouteCategory Context triple: [European route network, includesRouteCategory, main E-routes]
-
A.
includesRouteType
chosen
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
-
B.
containsCategory
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
-
C.
routeCategory
Indicates the classification or type assigned to a route within a transportation or path network.
-
D.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
-
E.
usesCategorySystem
Indicates that one entity organizes or classifies things according to a particular category system defined by 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_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.