Triple
T13351747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FBI ABSCAM operation |
E318085
|
entity |
| Predicate | usedRolePlayAs |
P87456
|
FINISHED |
| Object | wealthy Arab investors |
—
|
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: wealthy Arab investors | Statement: [FBI ABSCAM operation, usedRolePlayAs, wealthy Arab investors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRolePlayAs Context triple: [FBI ABSCAM operation, usedRolePlayAs, wealthy Arab investors]
-
A.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
B.
playsAs
chosen
Indicates that one entity performs, portrays, or assumes the role, character, or persona of another entity.
-
C.
characterRoleSwap
Indicates a relationship where two characters exchange or assume each other’s narrative roles or functions within a story or scenario.
-
D.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
E.
covertRole
Indicates that an entity holds or performs a hidden, secret, or undercover role in relation to another entity 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8c2f1c819094f0970f35f18afa |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6fd8bc819086dddb6f376efa57 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:32 p.m.