Triple
T36999018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icelandic Ring Road (Route 1) |
E915301
|
entity |
| Predicate | connectsMost |
P201063
|
FINISHED |
| Object | Icelandic towns |
—
|
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: Icelandic towns | Statement: [Icelandic Ring Road (Route 1), connectsMost, Icelandic towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsMost Context triple: [Icelandic Ring Road (Route 1), connectsMost, Icelandic towns]
-
A.
connectsBeyond
Indicates a relationship where one entity forms a link or association that extends past a usual boundary, scope, or intermediary to reach another entity.
-
B.
connectsMine
Indicates that one entity is linked or joined to another entity in the context of a mine or mining-related structure.
-
C.
connectsCommunity
Indicates a relationship where an entity links or brings together members or groups within a community, fostering interaction or cohesion among them.
-
D.
connectsPeak
Indicates a relationship where a path, route, or feature links one mountain peak directly to another.
-
E.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
- F. None of above. chosen
Provenance (4 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69ffc515e4b08190810b2a29b2885162 |
completed | May 9, 2026, 11:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.