Triple
T26921712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinder Downfall |
E677662
|
entity |
| Predicate | hasApproximateOSGridReference |
P10214
|
FINISHED |
| Object | SK 088 889 |
—
|
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: SK 088 889 | Statement: [Kinder Downfall, hasApproximateOSGridReference, SK 088 889]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateOSGridReference Context triple: [Kinder Downfall, hasApproximateOSGridReference, SK 088 889]
-
A.
hasOSGridReference
chosen
Indicates that an entity is associated with a specific Ordnance Survey grid reference location.
-
B.
hasIrishGridReference
Indicates that an entity is associated with a specific location identified by an Irish national grid reference coordinate.
-
C.
hasApproximateCoordinates
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
D.
gridReferenceType
Indicates the specific system or format used to express a location’s position within a spatial grid.
-
E.
hasApproximateLocation
Indicates that an entity is associated with a location that is known only imprecisely or within a general area rather than an exact position.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 6:07 a.m.