Triple
T4065200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEOWISE mission |
E86307
|
entity |
| Predicate | restarted |
P12197
|
FINISHED |
| Object | 2013-12 |
—
|
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: 2013-12 | Statement: [NEOWISE mission, restarted, 2013-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restarted Context triple: [NEOWISE mission, restarted, 2013-12]
-
A.
re-establishedAfter
Indicates that a relationship or state was previously ended or inactive and then brought back into effect following a specified event or time.
-
B.
relaunch
Indicates restarting or bringing back into operation something that was previously launched, often with changes or improvements.
-
C.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
D.
rebootOf
Indicates that one work is a new version that restarts or reimagines the story, continuity, or franchise of another earlier work.
-
E.
recommissioned
chosen
Indicates that something previously deactivated, retired, or out of service has been restored and formally returned to active use or operation.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.