Triple
T9034652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Jones and the Infernal Machine |
E216460
|
entity |
| Predicate | hasSaveSystem |
P44032
|
FINISHED |
| Object | checkpoint and manual saves |
—
|
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: checkpoint and manual saves | Statement: [Indiana Jones and the Infernal Machine, hasSaveSystem, checkpoint and manual saves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSaveSystem Context triple: [Indiana Jones and the Infernal Machine, hasSaveSystem, checkpoint and manual saves]
-
A.
saveSystem
chosen
Indicates performing an action that preserves or stores the current state or configuration of a system for future use or recovery.
-
B.
supportsCloudSaves
Indicates that one entity provides functionality for storing and retrieving save data in the cloud for another entity.
-
C.
savedWith
Indicates that one entity is preserved, stored, or kept together in association with another entity.
-
D.
hadImportPlayerSystem
Indicates that an entity utilized or was governed by a system for managing or handling imported players.
-
E.
hasRegisterSystem
Indicates that an entity uses or is associated with a particular register system (e.g., a system for recording, tracking, or registering items, events, or participants).
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6abf4af481908d21245332329d99 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.