Triple
T24360912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reykjanesbær |
E614052
|
entity |
| Predicate | distanceToReykjavík |
P72214
|
FINISHED |
| Object | approximately 47 km by road |
—
|
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: approximately 47 km by road | Statement: [Reykjanesbær, distanceToReykjavík, approximately 47 km by road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToReykjavík Context triple: [Reykjanesbær, distanceToReykjavík, approximately 47 km by road]
-
A.
distanceFromReykjavík
chosen
Indicates the spatial distance between an entity’s location and the city of Reykjavík.
-
B.
distanceFromKeflavíkAirport
Indicates the measured distance between a given location and Keflavík Airport.
-
C.
positionRelativeToReykjavík
Indicates the spatial position or location of an entity in relation to the city of Reykjavík.
-
D.
directionFromReykjavík
Indicates the cardinal or relative compass direction in which one entity is located from Reykjavík.
-
E.
distance to Tórshavn (kilometers)
Indicates the length, in kilometers, of the shortest travel distance between an entity and the location Tórshavn.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29383ccb88190a4752fe7ccd93fd5 |
completed | April 29, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2 a.m.