Triple
T33566889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American Datum of 1927 |
E859783
|
entity |
| Predicate | coordinateSystemDimension |
P6122
|
FINISHED |
| Object | 2D horizontal |
—
|
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 horizontal | Statement: [North American Datum of 1927, coordinateSystemDimension, 2D horizontal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateSystemDimension Context triple: [North American Datum of 1927, coordinateSystemDimension, 2D horizontal]
-
A.
coordinateSystem
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
B.
dimensionCount
chosen
Indicates the number of distinct dimensions or axes associated with an entity or data structure.
-
C.
formationDimension
Indicates the dimensional characteristics (such as size, scale, or extent) associated with the formation of something.
-
D.
dimensionSystem
Indicates a standardized framework or scheme used to define, measure, and relate dimensions within a given context.
-
E.
coordinateSystemBehavior
Indicates how positions, orientations, or transformations are defined, interpreted, and updated within a particular coordinate system.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 1:40 a.m.