Triple
T16566451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hipparcos |
E402473
|
entity |
| Predicate | primaryMirrorAperture |
P2517
|
FINISHED |
| Object | 29 cm |
—
|
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: 29 cm | Statement: [Hipparcos, primaryMirrorAperture, 29 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMirrorAperture Context triple: [Hipparcos, primaryMirrorAperture, 29 cm]
-
A.
primaryMirrorDiameter
chosen
Indicates the diameter of the primary mirror used in an optical system or instrument.
-
B.
secondaryMirrorDiameter
Indicates the diameter measurement of a system’s secondary mirror in a multi-mirror optical setup.
-
C.
auxiliaryTelescopeAperture
Indicates that one entity functions as the auxiliary telescope whose aperture (opening/diameter) is being specified or associated with another entity.
-
D.
twinTelescopeAperture
Indicates that two telescopes share the same aperture size or have apertures that are functionally equivalent.
-
E.
primaryMirrorArea
Indicates the surface area of the primary mirror involved in the optical or reflective system.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35772255881909f737da89bcd06b8 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.