Triple
T9034639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Jones and the Infernal Machine |
E216460
|
entity |
| Predicate | singlePlayer |
P43217
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Indiana Jones and the Infernal Machine, singlePlayer, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singlePlayer Context triple: [Indiana Jones and the Infernal Machine, singlePlayer, true]
-
A.
hasSinglePlayer
chosen
Indicates that something includes, supports, or is designed for a single-player mode or experience.
-
B.
singleWith
Indicates that an entity is unmarried and not currently in a romantic relationship.
-
C.
singleBy
Indicates that an entity is not in a romantic relationship and is considered single according to a specified criterion or context.
-
D.
onlySurvivingPlay
Indicates that the referenced work is the sole remaining play by a particular creator or from a specific set, with all others lost or no longer extant.
-
E.
signedPlayer
Indicates that an organization or team has formally entered into a contract or agreement with a player to join or represent them.
- 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.