Triple
T12439658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Family Secrets |
E297235
|
entity |
| Predicate | majorIndictmentsYear |
P66030
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Operation Family Secrets, majorIndictmentsYear, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorIndictmentsYear Context triple: [Operation Family Secrets, majorIndictmentsYear, 2005]
-
A.
dateFirstIndictmentsIssued
Indicates the date on which the first formal indictments in a particular case or investigation were officially issued.
-
B.
firstIndictmentIssued
Indicates that an initial formal criminal charge has been officially filed against an entity for the first time in a given case or context.
-
C.
notableCaseYear
chosen
Indicates the year in which a particular case became notable or gained recognized significance.
-
D.
numberOfIndictedPersonsApproximate
Indicates an approximate count of persons who have been formally indicted in a given context or case.
-
E.
notableIndictedLeaders
Indicates that the leaders associated with an entity are notable figures who have been formally indicted on criminal charges.
- 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.