Triple
T23185757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bessel ellipsoid |
E579588
|
entity |
| Predicate | computationBasis |
P6447
|
FINISHED |
| Object | astronomical observations |
—
|
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: astronomical observations | Statement: [Bessel ellipsoid, computationBasis, astronomical observations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computationBasis Context triple: [Bessel ellipsoid, computationBasis, astronomical observations]
-
A.
computationInput
Indicates that an entity serves as input data or parameters consumed by a computation or processing activity.
-
B.
computationalClass
Indicates that two entities share the same computational complexity class or that one entity is categorized within a specified computational complexity class.
-
C.
computes
Indicates that one entity performs a calculation or processing operation to produce a result from given data or inputs.
-
D.
proposedRepresentationBasis
Indicates that one entity has been put forward as the foundational or reference basis for representing or encoding another entity.
-
E.
calculationBasis
chosen
Indicates the rule, method, or reference standard used as the foundation for performing a calculation in the relationship.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f7230208190820acf52f537b3ff |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.