Triple
T33566764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATRF2022 |
E859780
|
entity |
| Predicate | usesReferenceEllipsoid |
P60848
|
FINISHED |
| Object | GRS80 |
—
|
NE NERFINISHED |
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: GRS80 | Statement: [NATRF2022, usesReferenceEllipsoid, GRS80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReferenceEllipsoid Context triple: [NATRF2022, usesReferenceEllipsoid, GRS80]
-
A.
usesEllipsoid
chosen
Indicates that one entity employs or is based on a particular ellipsoid as its geometric or reference model.
-
B.
geodeticReference
Indicates a relationship where one spatial or geographic entity is defined, measured, or located with respect to a specific geodetic reference system or datum.
-
C.
isLocalDatumEllipsoid
Indicates that a geodetic datum is defined relative to a specific local reference ellipsoid rather than a global one.
-
D.
isReferenceSystemFor
Indicates that one system serves as the coordinate or measurement framework used to define, locate, or describe positions or values in another system.
-
E.
usesEarthOblateness
Indicates that something takes into account or relies on the Earth's non-spherical (oblate) shape in its calculations or operations.
- 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_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:40 a.m.