Triple
T16981220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airy Modified ellipsoid |
E411948
|
entity |
| Predicate | datumRealization |
P39259
|
FINISHED |
| Object | OSI 1965 |
—
|
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: OSI 1965 | Statement: [Airy Modified ellipsoid, datumRealization, OSI 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datumRealization Context triple: [Airy Modified ellipsoid, datumRealization, OSI 1965]
-
A.
hasRealizationAs
chosen
Indicates that something abstract, such as a plan, design, or concept, is concretely implemented or manifested as a particular realized form.
-
B.
finalRealization
Indicates the culminating recognition or understanding that occurs at the end of a process, event, or sequence of actions.
-
C.
datumUsed
Indicates that a particular piece of data is utilized or referenced in performing an action, process, or relation.
-
D.
realizationMethod
Indicates the means, process, or technique by which something is carried out, implemented, or brought into effect.
-
E.
oftenRealizedIn
Indicates that something typically manifests, occurs, or is expressed within a particular context, medium, or setting.
- 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.