Triple
T25609668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christo Grozev |
E642011
|
entity |
| Predicate | hasNotableInvestigationTopic |
P175610
|
FINISHED |
| Object | Russian GRU |
—
|
NE NERFINISHED |
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: Russian GRU | Statement: [Christo Grozev, hasNotableInvestigationTopic, Russian GRU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableInvestigationTopic Context triple: [Christo Grozev, hasNotableInvestigationTopic, Russian GRU]
-
A.
hasNotableSubject
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
-
B.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
-
C.
containsInvestigationOf
Indicates that one entity includes or encompasses an investigation or inquiry concerning another entity.
-
D.
hasInvestigationTarget
chosen
Indicates that an investigation is directed toward or focused on a particular target entity.
-
E.
areInvestigatedFor
Indicates that one or more entities are the subject of an investigation concerning a particular issue, incident, or alleged wrongdoing.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 21, 2026, 4:40 p.m.