Triple
T4874744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumburgh Airport |
E109172
|
entity |
| Predicate | distanceToLerwickKilometers |
P60388
|
FINISHED |
| Object | about 40 |
—
|
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: about 40 | Statement: [Sumburgh Airport, distanceToLerwickKilometers, about 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLerwickKilometers Context triple: [Sumburgh Airport, distanceToLerwickKilometers, about 40]
-
A.
distanceFromCopenhagen
Indicates the spatial distance between a given entity and the location of Copenhagen.
-
B.
distanceFromOslo
Indicates the spatial distance between a given entity’s location and the city of Oslo.
-
C.
distanceToOuterHebrides
Indicates the measured distance between a given entity’s location and the Outer Hebrides.
-
D.
distanceToSunderland_km
Indicates the physical distance, measured in kilometers, between a given place and Sunderland.
-
E.
distanceToAberdeen
Indicates the spatial distance between a given entity and the location of Aberdeen.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:27 p.m.