Triple
T26105965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inch Talla |
E658535
|
entity |
| Predicate | isInNationalGridReferenceSystem |
P159954
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Inch Talla, isInNationalGridReferenceSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInNationalGridReferenceSystem Context triple: [Inch Talla, isInNationalGridReferenceSystem, yes]
-
A.
isReferenceSystemFor
Indicates that one system serves as the coordinate or measurement framework used to define, locate, or describe positions or values in another system.
-
B.
hasGeographicalCoordinateSystem
Indicates that something uses or is defined within a specific geographical coordinate system for locating positions on the Earth’s surface.
-
C.
hasIrishGridReference
Indicates that an entity is associated with a specific location identified by an Irish national grid reference coordinate.
-
D.
hasOSGridReference
Indicates that an entity is associated with a specific Ordnance Survey grid reference location.
-
E.
gridReferenceType
Indicates the specific system or format used to express a location’s position within a spatial grid.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f607774de48190ba59eb5bfeaf3d5d |
completed | May 2, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 7:58 p.m.