Triple
T22058121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V838 Monocerotis |
E545074
|
entity |
| Predicate | notableImageDate |
P1156
|
FINISHED |
| Object | Hubble observations in 2002 |
—
|
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: Hubble observations in 2002 | Statement: [V838 Monocerotis, notableImageDate, Hubble observations in 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableImageDate Context triple: [V838 Monocerotis, notableImageDate, Hubble observations in 2002]
-
A.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
dateDepicted
Indicates that one entity specifies the calendar date on which the other entity, typically an event or scene, is depicted as occurring.
-
C.
notableDepictionYear
chosen
Indicates the year in which a notable or significant depiction of an entity occurred or was created.
-
D.
notableCaseDate
Indicates the date on which a particular case or legal matter became notable or was formally recognized as significant.
-
E.
notableOperationDate
Indicates the date on which a significant or noteworthy operation, event, or activity associated with an entity took place.
- 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.