Triple
T32101837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilson sisters |
E819869
|
entity |
| Predicate | impersonatedBy |
P20150
|
FINISHED |
| Object | Kevin Copeland |
—
|
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: Kevin Copeland | Statement: [Wilson sisters, impersonatedBy, Kevin Copeland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impersonatedBy Context triple: [Wilson sisters, impersonatedBy, Kevin Copeland]
-
A.
allegedImpostor
Indicates that one entity is claimed or suspected to be fraudulently posing as another entity.
-
B.
canImpersonate
Indicates that one entity has the ability or permission to act as or represent another entity, typically assuming its identity or role.
-
C.
killsOnBehalfOf
Indicates that one entity kills another while acting under the direction, authority, or interests of a third party.
-
D.
presentedOnBehalfOf
Indicates that an action, statement, or presentation was made by one party while formally representing or acting for another party.
-
E.
disguisedAs
chosen
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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b696b7d48190b726125893d69522 |
completed | May 3, 2026, 2:44 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:26 a.m.