Triple
T8498819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicky Parsons |
E201163
|
entity |
| Predicate | hasInsiderKnowledgeOf |
P71015
|
FINISHED |
| Object | CIA covert operations |
—
|
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: CIA covert operations | Statement: [Nicky Parsons, hasInsiderKnowledgeOf, CIA covert operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInsiderKnowledgeOf Context triple: [Nicky Parsons, hasInsiderKnowledgeOf, CIA covert operations]
-
A.
knowsSecret
chosen
Indicates that one entity is aware of confidential or hidden information about another entity or situation.
-
B.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
C.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
D.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
E.
hasLimitedAuthorityOver
Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5984d7481908c41c57bef9cf254 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.