Triple
T206478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moon |
E4619
|
entity |
| Predicate | apparentMagnitudeAtFull |
P7282
|
FINISHED |
| Object | about −12.7 |
—
|
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: about −12.7 | Statement: [Moon, apparentMagnitudeAtFull, about −12.7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apparentMagnitudeAtFull Context triple: [Moon, apparentMagnitudeAtFull, about −12.7]
-
A.
apparentMagnitude
chosen
Indicates the observed brightness of an astronomical object as seen from Earth, on a logarithmic scale where lower values correspond to brighter appearances.
-
B.
apparentMagnitudeV
Indicates the visual brightness of an astronomical object as seen from Earth, measured in the V (visual) band of the electromagnetic spectrum.
-
C.
luminosityRelativeToSun
Indicates how bright an object is compared to the Sun, expressed as a ratio of their luminosities.
-
D.
brightestStarApparentMagnitude
Indicates the apparent brightness value (magnitude) of the brightest star as seen from a given observation point.
-
E.
brightestStar
Indicates that one entity is the most luminous star within a specified group, region, or context relative to the others.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.