Triple
T3825364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIA Special Activities Division |
E88672
|
entity |
| Predicate | usesPersonnelFrom |
P51517
|
FINISHED |
| Object | CIA officers |
—
|
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 officers | Statement: [CIA Special Activities Division, usesPersonnelFrom, CIA officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPersonnelFrom Context triple: [CIA Special Activities Division, usesPersonnelFrom, CIA officers]
-
A.
personnel
Indicates that an entity serves as staff or workforce associated with another entity, such as an organization, project, or facility.
-
B.
personnelSource
chosen
Indicates the origin or provider from which personnel are obtained or assigned.
-
C.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
D.
personnelComposition
Indicates the makeup or distribution of people or roles within a group, organization, or unit.
-
E.
authorizedPersonnel
Indicates that the referenced entity is officially permitted or empowered to access, use, or perform actions within a specified system, resource, or context.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.