Triple
T16981218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airy Modified ellipsoid |
E411948
|
entity |
| Predicate | hasInverseFlattening |
P18362
|
FINISHED |
| Object | 299.3249646 |
—
|
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: 299.3249646 | Statement: [Airy Modified ellipsoid, hasInverseFlattening, 299.3249646]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInverseFlattening Context triple: [Airy Modified ellipsoid, hasInverseFlattening, 299.3249646]
-
A.
inverseFlattening
chosen
Indicates the reciprocal of the flattening ratio of an ellipsoid, expressing how much it deviates from a perfect sphere.
-
B.
hasFlat
Indicates that an entity possesses or is associated with a flat (an apartment or level dwelling unit).
-
C.
isFlat
Indicates that something has a level, even, or smooth surface without significant curves, bumps, or elevations.
-
D.
flattening
Indicates that one entity causes another entity to become flat or more level, reducing its height, thickness, or irregularities.
-
E.
hasInversionCapability
Indicates that an entity possesses the ability to reverse or invert another entity, state, or process.
- 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_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. |
Created at: April 10, 2026, 5:32 a.m.