Triple
T3886083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SN 1954J |
E92943
|
entity |
| Predicate | followUpObservations |
P26705
|
FINISHED |
| Object | late-time imaging of the site |
—
|
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: late-time imaging of the site | Statement: [SN 1954J, followUpObservations, late-time imaging of the site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followUpObservations Context triple: [SN 1954J, followUpObservations, late-time imaging of the site]
-
A.
followsUp
Indicates that one entity continues, responds to, or builds upon a previous entity, typically as a subsequent action, communication, or step.
-
B.
hasObservation
chosen
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
-
C.
followUpRelease
Indicates that one release occurs subsequently as a continuation or update to a previous release.
-
D.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
E.
alsoObservedOn
Indicates that the same entity, event, or phenomenon was additionally observed on another occasion, date, or context beyond the primary one referenced.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec942bfc8190a398fe370715a28b |
completed | March 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.