Triple
T957482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC4 |
E20655
|
entity |
| Predicate | specificationLeakedIn |
P21842
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [RC4, specificationLeakedIn, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specificationLeakedIn Context triple: [RC4, specificationLeakedIn, 1994]
-
A.
hasSpecification
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
B.
unveiledOn
Indicates the date or event at which something (such as a product, artwork, or plan) was formally revealed or made public.
-
C.
unveiledBy
Indicates that something (such as an object, artwork, or project) was formally revealed or presented to the public by a particular agent or entity.
-
D.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
E.
hasModeOfRevelation
Indicates the manner or channel through which something is revealed, communicated, or made known.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3fac2bc8190a66feb70c68899b2 |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a18ecc8190883f6206fe3b0fb6 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b326d9d88190913c1a892a795707 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.