Triple
T23736670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PZ-90 |
E586557
|
entity |
| Predicate | referenceEllipsoid |
P60848
|
FINISHED |
| Object | PZ-90 reference ellipsoid |
—
|
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: PZ-90 reference ellipsoid | Statement: [PZ-90, referenceEllipsoid, PZ-90 reference ellipsoid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceEllipsoid Context triple: [PZ-90, referenceEllipsoid, PZ-90 reference ellipsoid]
-
A.
usesEllipsoid
chosen
Indicates that one entity employs or is based on a particular ellipsoid as its geometric or reference model.
-
B.
referenceSurface
Indicates that one entity serves as the surface or base relative to which another entity is positioned, aligned, or defined.
-
C.
isLocalDatumEllipsoid
Indicates that a geodetic datum is defined relative to a specific local reference ellipsoid rather than a global one.
-
D.
hasEquatorialRadius
Indicates that an entity has a specified radius measured at its equator.
-
E.
referenceMeridian
Indicates that one location, measurement, or coordinate system is defined or interpreted relative to a specified meridian used as its longitudinal reference.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad28fa481909d7a6a6e98a7b0a5 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:10 p.m.