Triple
T21442928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EN |
E528984
|
entity |
| Predicate | denotesNetworkType |
P3937
|
FINISHED |
| Object | national road network |
—
|
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: national road network | Statement: [EN, denotesNetworkType, national road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesNetworkType Context triple: [EN, denotesNetworkType, national road network]
-
A.
networkType
chosen
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
B.
providesNetworkType
Indicates that one entity supplies or specifies the type of network associated with another entity.
-
C.
routeNetworkType
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
-
D.
definesNetwork
Indicates that one entity specifies or establishes the structure, configuration, or boundaries of a network for another entity.
-
E.
intendedNetwork
Indicates the network that an entity is planned, designed, or expected to connect to or operate within.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b7044a3881908a7fe26f26c92762 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:05 p.m.