Triple
T9970346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All the Money in the World |
E196185
|
entity |
| Predicate | reshootsCompletedIn |
P1574
|
FINISHED |
| Object | 2017-11 |
—
|
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: 2017-11 | Statement: [All the Money in the World, reshootsCompletedIn, 2017-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reshootsCompletedIn Context triple: [All the Money in the World, reshootsCompletedIn, 2017-11]
-
A.
completedIn
chosen
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
B.
numberOfSurvivingTakes
Indicates the count of takes or attempts that successfully remained valid or usable after others were discarded or failed.
-
C.
rebuiltCompletedIn
Indicates that an entity has undergone a rebuilding process that was fully completed in a specified time or event.
-
D.
alsoCompletedBy
Indicates that the same task, activity, or item has been completed by an additional agent or entity besides the one already referenced.
-
E.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7b7ea9881908a56f11e2e446dd0 |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:48 p.m.