Triple
T16981232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airy Modified ellipsoid |
E411948
|
entity |
| Predicate | isLocalDatumEllipsoid |
P125470
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Airy Modified ellipsoid, isLocalDatumEllipsoid, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocalDatumEllipsoid Context triple: [Airy Modified ellipsoid, isLocalDatumEllipsoid, true]
-
A.
usesEllipsoid
Indicates that one entity employs or is based on a particular ellipsoid as its geometric or reference model.
-
B.
isGeocentric
Indicates that something is centered around, or takes the Earth as the central reference point in, a spatial or cosmological framework.
-
C.
hasEquatorialRadius
Indicates that an entity has a specified radius measured at its equator.
-
D.
hasGeodeticPurpose
Indicates that something is associated with or serves a specific geodetic purpose, such as measurement, reference, or positioning in geodesy.
-
E.
hasApproximateDistanceFromEquator
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18776c081909225620fd43aca57 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:32 a.m.