Triple
T35772983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Explorer 6 |
E1034213
|
entity |
| Predicate | endOfUsefulOperations |
P184901
|
FINISHED |
| Object | 1959-10-06 |
—
|
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: 1959-10-06 | Statement: [Explorer 6, endOfUsefulOperations, 1959-10-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfUsefulOperations Context triple: [Explorer 6, endOfUsefulOperations, 1959-10-06]
-
A.
finalOperations
Indicates that an entity is involved in the last or concluding set of actions or processes within a sequence or workflow.
-
B.
endOfUndergroundOperation
Indicates the point in time or event at which an underground operation or activity is concluded or terminated.
-
C.
cleanupOperation
Indicates an action where an entity removes, resets, or tidies up residual data, resources, or state after a process or event has completed.
-
D.
ceasedOperationAfter
Indicates that one entity stopped functioning, operating, or being active after another specified event or entity’s operation ended.
-
E.
useEnded
Indicates that an entity’s period of using or employing another entity has come to an end.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: May 3, 2026, 4:06 p.m.