Triple
T18956706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 32 |
E463797
|
entity |
| Predicate | minorAxisAngularSize_arcmin |
P133950
|
FINISHED |
| Object | 6.4 |
—
|
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: 6.4 | Statement: [Messier 32, minorAxisAngularSize_arcmin, 6.4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minorAxisAngularSize_arcmin Context triple: [Messier 32, minorAxisAngularSize_arcmin, 6.4]
-
A.
angularSize
Indicates the apparent size of an object as seen from a given point, typically measured as the angle it subtends at the observer.
-
B.
primaryMirrorDiameter
Indicates the diameter of the primary mirror used in an optical system or instrument.
-
C.
semiMajorAxis
Indicates the length of the longest radius of an elliptical orbit, measuring the average distance between the orbiting body and the central body.
-
D.
secondaryMirrorDiameter
Indicates the diameter measurement of a system’s secondary mirror in a multi-mirror optical setup.
-
E.
auxiliaryTelescopeAperture
Indicates that one entity functions as the auxiliary telescope whose aperture (opening/diameter) is being specified or associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5cdf2d08190a0aecd3fa5335a75 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, noon