Triple
T5507462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio |
E144475
|
entity |
| Predicate | participatesInHeist |
P46944
|
FINISHED |
| Object | Royal Mint of Spain heist |
—
|
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: Royal Mint of Spain heist | Statement: [Rio, participatesInHeist, Royal Mint of Spain heist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatesInHeist Context triple: [Rio, participatesInHeist, Royal Mint of Spain heist]
-
A.
partnerInCrime
Indicates a relationship where two or more entities collaborate closely in committing or planning wrongful, illicit, or mischievous acts together.
-
B.
roleInCrime
chosen
Indicates the specific function, responsibility, or participation an entity has within the commission of a particular crime.
-
C.
lootedBy
Indicates that something has been forcibly taken or plundered by a specified agent or group.
-
D.
criminalOrganization
Indicates that the subject is an organized group engaged in ongoing illegal activities, often with structured hierarchy and coordination.
-
E.
notableHeistTarget
Indicates that an entity is a significant or high-profile target of a heist or major theft.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f495c588190b0cfe5bfb3d2c221 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.