Triple
T13091655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colossus computers |
E310475
|
entity |
| Predicate | declassificationDate |
P48219
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Colossus computers, declassificationDate, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declassificationDate Context triple: [Colossus computers, declassificationDate, 1970s]
-
A.
declassified
Indicates that information or material has been officially downgraded from a restricted or secret status, making it accessible to a wider audience or the public.
-
B.
canBeDeclassifiedBy
Indicates that an item currently classified or restricted may be lawfully downgraded or released by a specified authority or entity.
-
C.
mayBeDeclassified
Indicates that an item currently classified or restricted is eligible or permitted to have its classification status removed or lowered.
-
D.
yearOfPublicDisclosure
chosen
Indicates the calendar year in which information, an invention, or other subject matter was first publicly disclosed.
-
E.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813acbac8190b2fe5e07287457cf |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.