Triple
T28393630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horns Rev 2 |
E719220
|
entity |
| Predicate | distanceFromEsbjerg |
P201489
|
FINISHED |
| Object | approximately 30–35 km |
—
|
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 30–35 km | Statement: [Horns Rev 2, distanceFromEsbjerg, approximately 30–35 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromEsbjerg Context triple: [Horns Rev 2, distanceFromEsbjerg, approximately 30–35 km]
-
A.
distanceFromCopenhagen
Indicates the spatial distance between a given entity and the location of Copenhagen.
-
B.
distanceFromArendal
Indicates the spatial distance between a given entity and the location of Arendal.
-
C.
distanceToFlensburg_km
Indicates the distance, measured in kilometers, between a given entity’s location and the city of Flensburg.
-
D.
distanceFromLongyearbyen
Indicates the measured distance between a given location and Longyearbyen.
-
E.
distanceToHelsingør
Indicates the spatial distance between an entity and the location of Helsingør.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69fffbb513c881909063ecf12467f4a6 |
completed | May 10, 2026, 3:29 a.m. |
Created at: April 28, 2026, 1:15 a.m.