Triple
T5043921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C/1996 B2 |
E113612
|
entity |
| Predicate | apparentMagnitudeAtPeak |
P7282
|
FINISHED |
| Object | about 0 |
—
|
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 0 | Statement: [C/1996 B2, apparentMagnitudeAtPeak, about 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apparentMagnitudeAtPeak Context triple: [C/1996 B2, apparentMagnitudeAtPeak, about 0]
-
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.
lightcurveAmplitude
Indicates the measured range of brightness variation of an object over time in its light curve.
-
C.
apparentMagnitudeV
Indicates the visual brightness of an astronomical object as seen from Earth, measured in the V (visual) band of the electromagnetic spectrum.
-
D.
absoluteMagnitudeV
Indicates the intrinsic brightness of an astronomical object in the visual (V) band, standardized to a fixed reference distance (typically 10 parsecs).
-
E.
apparentBrightness
Indicates how bright one object appears from the perspective or location of another, regardless of its actual intrinsic luminosity.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fc04f08190aba851fa0192d0fb |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.