Triple
T33566904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American Datum of 1927 |
E859783
|
entity |
| Predicate | coordinateDifferencesRelativeTo |
P180574
|
FINISHED |
| Object | NAD83 |
—
|
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: NAD83 | Statement: [North American Datum of 1927, coordinateDifferencesRelativeTo, NAD83]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateDifferencesRelativeTo Context triple: [North American Datum of 1927, coordinateDifferencesRelativeTo, NAD83]
-
A.
pointDifference
Indicates the numerical difference in points or scores between two compared entities.
-
B.
movesRelativeTo
Indicates that one entity changes its position or orientation with respect to another entity, rather than with respect to a fixed reference frame.
-
C.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
-
D.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
E.
coordinateOf
Indicates that one entity specifies the spatial or positional coordinates associated with another entity.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: May 1, 2026, 1:40 a.m.