Triple
T27399280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A99 road |
E691784
|
entity |
| Predicate | onMainlandOf |
P67139
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [A99 road, onMainlandOf, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onMainlandOf Context triple: [A99 road, onMainlandOf, United Kingdom]
-
A.
isMainlandTerritoryOf
Indicates that a territory constitutes the primary continental landmass belonging to a particular country or sovereign entity.
-
B.
terminalOnMainland
Indicates that a transportation or service terminal is physically located on the mainland rather than on an island or offshore location.
-
C.
connectedToMainlandBy
Indicates that one landmass or area is physically linked to a mainland, typically via a bridge, causeway, or other continuous connection.
-
D.
appliesToMainland
chosen
Indicates that something is relevant or applicable specifically to the mainland portion of a territory, excluding its islands or overseas areas.
-
E.
isRemoteFromMainland
Indicates that a location is geographically separated and distant from the primary mainland area of a region or country.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:28 p.m.