Triple
T27479568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byrum |
E693561
|
entity |
| Predicate | hasRoadConnectionWithinIsland |
P120973
|
FINISHED |
| Object | Læsø 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: Læsø road network | Statement: [Byrum, hasRoadConnectionWithinIsland, Læsø road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadConnectionWithinIsland Context triple: [Byrum, hasRoadConnectionWithinIsland, Læsø road network]
-
A.
isRoadConnectedWithinIsland
chosen
Indicates that two locations on the same island are connected by a continuous road network without leaving the island.
-
B.
hasIslandConnection
Indicates that there exists a connection or link between entities that specifically involves or passes through an island.
-
C.
hasRoadConnectionRegion
Indicates that there is a road-based transportation link connecting one region to another.
-
D.
isRoadTrafficFreeIslandLink
Indicates that a road connection between an island and the mainland (or another island) is free of traffic congestion.
-
E.
hasBridgeOrFerryConnection
Indicates that there exists a bridge or ferry link enabling direct passage or transport between the related entities.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 12:58 p.m.