Triple
T28600316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spain |
E723891
|
entity |
| Predicate | sharesMotorwayNetworkWith |
P152345
|
FINISHED |
| Object | France |
—
|
NE NERFINISHED |
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: France | Statement: [Spain, sharesMotorwayNetworkWith, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesMotorwayNetworkWith Context triple: [Spain, sharesMotorwayNetworkWith, France]
-
A.
motorwayServedBy
Indicates that a motorway is connected to or accessed by a particular service facility, route, or transport service.
-
B.
isMotorwayIn
Indicates that a motorway is located within or passes through a specified geographic area or administrative region.
-
C.
motorwayConnectionWith
chosen
Indicates that two locations are directly connected by a motorway, allowing vehicular travel between them via that road.
-
D.
nationalHighwayConnectivity
Indicates the extent to which locations are linked by a network of national highways enabling direct or efficient road travel between them.
-
E.
shareTransportInfrastructure
Indicates that multiple entities make joint use of the same transport infrastructure facilities or systems.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: April 28, 2026, 4:24 a.m.