Triple
T35561154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WISE |
E1027637
|
entity |
| Predicate | reactivatedMissionType |
P22637
|
FINISHED |
| Object | near-Earth object survey |
—
|
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: near-Earth object survey | Statement: [WISE, reactivatedMissionType, near-Earth object survey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactivatedMissionType Context triple: [WISE, reactivatedMissionType, near-Earth object survey]
-
A.
returnMission
Indicates that an entity goes back to its original location or base after completing a mission or task.
-
B.
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.
-
C.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
D.
reactivatedDuring
Indicates that an entity becomes active again within the time span or context defined by another event or condition.
-
E.
enabledMission
Indicates that a mission has been activated or made available for execution or participation.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.