Triple
T36998995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icelandic Ring Road (Route 1) |
E915301
|
entity |
| Predicate | followsRouteShape |
P199803
|
FINISHED |
| Object | ring around Iceland |
—
|
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: ring around Iceland | Statement: [Icelandic Ring Road (Route 1), followsRouteShape, ring around Iceland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsRouteShape Context triple: [Icelandic Ring Road (Route 1), followsRouteShape, ring around Iceland]
-
A.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
B.
servesAsRouteTo
Indicates that one entity functions as a pathway, channel, or means of access leading to another entity.
-
C.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
D.
hasRouteAlignment
Indicates that there is a defined spatial or geometric alignment associated with a route or pathway.
-
E.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
- 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_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
| PDg | Predicate description generation | batch_69ff58031bb081909fea985b16f69da4 |
completed | May 9, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:14 p.m.