Triple
T5903320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airy disk |
E131279
|
entity |
| Predicate | hasAngularRadius |
P6952
|
FINISHED |
| Object | 1.22 λ / D |
—
|
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: 1.22 λ / D | Statement: [Airy disk, hasAngularRadius, 1.22 λ / D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAngularRadius Context triple: [Airy disk, hasAngularRadius, 1.22 λ / D]
-
A.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
B.
hasRadius_solarRadius
Indicates that an entity has a radius whose value is expressed in units of the Sun’s radius.
-
C.
hasRadiusType
Indicates that an entity has a radius characterized by a specific type or classification.
-
D.
angularSize
chosen
Indicates the apparent size of an object as seen from a given point, typically measured as the angle it subtends at the observer.
-
E.
hasPolarRadius
Indicates that an entity possesses a specific radius measured from its center to its pole, typically used for spheroidal or planetary bodies.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.