Triple
T22058100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V838 Monocerotis |
E545074
|
entity |
| Predicate | lightEcho |
P60193
|
FINISHED |
| Object | observed after 2002 outburst |
—
|
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: observed after 2002 outburst | Statement: [V838 Monocerotis, lightEcho, observed after 2002 outburst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightEcho Context triple: [V838 Monocerotis, lightEcho, observed after 2002 outburst]
-
A.
lightEchoesObserved
chosen
Indicates that light from an earlier event has been observed after reflecting or scattering off intervening material, producing a detectable light echo.
-
B.
lightPath
Indicates the route or trajectory that light follows as it travels between entities or through a medium.
-
C.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
D.
echoedIn
Indicates that a sound, statement, or effect produced in one context is repeated, reflected, or resonated in another context.
-
E.
lightFunction
Indicates that one entity serves as a source or means of illumination or lighting for another entity or context.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285959f48190b89527b3f9e7ab11 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.