Triple
T9924561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth Jane Cochran |
E187887
|
entity |
| Predicate | usedUndercoverMethods |
P22080
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Elizabeth Jane Cochran, usedUndercoverMethods, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedUndercoverMethods Context triple: [Elizabeth Jane Cochran, usedUndercoverMethods, yes]
-
A.
undercoverAgainst
Indicates that one entity is secretly acting in a covert or deceptive capacity directed against another entity.
-
B.
usedSecretPolice
Indicates that an entity employed or relied on secret police forces to monitor, control, or repress others.
-
C.
usesMasksOrDisguises
chosen
Indicates that an entity employs masks, costumes, or other forms of disguise to conceal or alter its identity in the context of an action or interaction.
-
D.
usesInvestigativeMethods
Indicates that an entity employs investigative techniques or procedures to gather information, analyze evidence, or uncover facts.
-
E.
disguisedAs
Indicates that one entity is intentionally presenting itself as, or made to appear as, another entity in order to conceal its true identity.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb598651081908286763ff56ba57c |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.