Triple
T34294576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R67 road |
E879986
|
entity |
| Predicate | linksInlandAreasWith |
P139192
|
FINISHED |
| Object | major national roads |
—
|
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: major national roads | Statement: [R67 road, linksInlandAreasWith, major national roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linksInlandAreasWith Context triple: [R67 road, linksInlandAreasWith, major national roads]
-
A.
connectsInlandRoutesTo
chosen
Indicates that one entity serves as a link or junction that enables inland transportation routes to reach or connect with another entity.
-
B.
connectsInlandCommunitiesTo
Indicates a relationship in which something serves as a link or conduit between inland communities and another place, system, or network.
-
C.
connectsInlandToBorder
Indicates that an inland location is linked or provides a route to a border location.
-
D.
connectsCoastToInland
Indicates a relationship where something (such as a route, structure, or feature) links a coastal area to an inland area.
-
E.
linkedToInlandPort
Indicates a relationship where something has a direct connection or association with an inland port, such as for transport, logistics, or access purposes.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.