Triple
T29190914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellagio vault robbery |
E739986
|
entity |
| Predicate | involvesCrew |
P24309
|
FINISHED |
| Object | Rusty Ryan |
—
|
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: Rusty Ryan | Statement: [Bellagio vault robbery, involvesCrew, Rusty Ryan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesCrew Context triple: [Bellagio vault robbery, involvesCrew, Rusty Ryan]
-
A.
crewInvolvedIn
chosen
Indicates that a crew (as a group or unit) participates in, contributes to, or is otherwise involved in a specified event, activity, or operation.
-
B.
intendedCrew
Indicates that an entity is designated or planned to serve as the crew for another entity (such as a vehicle, mission, or operation).
-
C.
refersToCrew
Indicates that one entity makes reference to, is associated with, or pertains to a specific crew or group of crew members.
-
D.
hasCrewFeature
Indicates that a crew possesses or is characterized by a particular feature, attribute, or capability.
-
E.
hasCrewRole
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 28, 2026, 12:02 p.m.