Triple
T4073253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish grid reference system |
E86697
|
entity |
| Predicate | coordinateReferenceDimension |
P6122
|
FINISHED |
| Object | 2D |
—
|
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: 2D | Statement: [Irish grid reference system, coordinateReferenceDimension, 2D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateReferenceDimension Context triple: [Irish grid reference system, coordinateReferenceDimension, 2D]
-
A.
coordinateSystem
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
B.
dimensionSystem
Indicates a standardized framework or scheme used to define, measure, and relate dimensions within a given context.
-
C.
dimensionType
Indicates the specific kind or category of dimension that characterizes how something is measured or structured.
-
D.
dimensionCount
chosen
Indicates the number of distinct dimensions or axes associated with an entity or data structure.
-
E.
coordinateTransformation
Indicates a relationship where one coordinate system is mathematically converted or mapped into another, preserving the correspondence of points between them.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc22be988190a2b6575d4f5e0f7b |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.