Triple
T9034647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Jones and the Infernal Machine |
E216460
|
entity |
| Predicate | plotGoal |
P42284
|
FINISHED |
| Object | stop Soviet plot |
—
|
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: stop Soviet plot | Statement: [Indiana Jones and the Infernal Machine, plotGoal, stop Soviet plot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plotGoal Context triple: [Indiana Jones and the Infernal Machine, plotGoal, stop Soviet plot]
-
A.
narrativeGoal
chosen
Indicates that one entity has a desired outcome or objective within a story or narrative context that drives their actions or development.
-
B.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
C.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
D.
allegedGoal
Indicates that one entity is claimed or reported to have the goal or intended objective of another entity, without asserting that the goal is actually true.
-
E.
gameObjective
Indicates the primary goal or intended outcome that participants aim to achieve within a game.
- 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.