Triple
T35561153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WISE |
E1027637
|
entity |
| Predicate | reactivatedName |
P183406
|
FINISHED |
| Object | NEOWISE |
—
|
NE NERFINISHED |
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: NEOWISE | Statement: [WISE, reactivatedName, NEOWISE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactivatedName Context triple: [WISE, reactivatedName, NEOWISE]
-
A.
reactivatedFrom
Indicates that an entity has been brought back into an active state from a previously inactive, archived, or decommissioned state, often referencing the source state or version it was reactivated from.
-
B.
reactivatedDuring
Indicates that an entity becomes active again within the time span or context defined by another event or condition.
-
C.
reestablishedUnderCurrentName
Indicates that an entity previously existed under a different name and was later reestablished using its current name.
-
D.
reactivationPossible
Indicates that a previously inactive or deactivated entity can be returned to an active or operational state.
-
E.
reactivationOutcome
Indicates the result or consequence that follows from a reactivation event or process.
- F. None of above. chosen
Provenance (4 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.