Triple
T29434883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bank |
E746541
|
entity |
| Predicate | securitySystemSabotagedBy |
P106847
|
FINISHED |
| Object | Ocean's crew |
—
|
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: Ocean's crew | Statement: [The Bank, securitySystemSabotagedBy, Ocean's crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securitySystemSabotagedBy Context triple: [The Bank, securitySystemSabotagedBy, Ocean's crew]
-
A.
securityApparatusControl
Indicates that one entity exercises authority over, manages, or directs the operations and decisions of a security or law-enforcement apparatus.
-
B.
sideDenyingIntrusion
Indicates that one side is actively preventing or rejecting an attempted intrusion by another.
-
C.
roleInSabotage
chosen
Indicates that an entity participated in or had a specific role in an act of sabotage.
-
D.
securityFigure
Indicates that one entity serves as a protective or safeguarding presence for another, typically responsible for ensuring its safety or security.
-
E.
securityApparatusRole
Indicates the role or function an entity holds within a security or law-enforcement apparatus.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 28, 2026, 3:15 p.m.