Triple
T29823440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mellie Logan |
E757313
|
entity |
| Predicate | helpsExecute |
P67492
|
FINISHED |
| Object | Logan Lucky 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: Logan Lucky heist | Statement: [Mellie Logan, helpsExecute, Logan Lucky heist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpsExecute Context triple: [Mellie Logan, helpsExecute, Logan Lucky heist]
-
A.
helpsIn
Indicates that one entity provides assistance, support, or aid to another entity in performing or achieving a particular task, activity, or goal.
-
B.
helpsProsecute
Indicates that one entity assists another entity in carrying out a legal prosecution against a target.
-
C.
helpsOrchestrate
chosen
Indicates involvement in coordinating, organizing, or managing the execution of an activity or process, often in collaboration with others.
-
D.
executedWith
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
-
E.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:30 p.m.