Triple
T29714775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Curse of Monkey Island |
E751877
|
entity |
| Predicate | hasPuzzleType |
P74559
|
FINISHED |
| Object | inventory-based puzzles |
—
|
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: inventory-based puzzles | Statement: [The Curse of Monkey Island, hasPuzzleType, inventory-based puzzles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPuzzleType Context triple: [The Curse of Monkey Island, hasPuzzleType, inventory-based puzzles]
-
A.
puzzleType
chosen
Indicates the specific category or kind of puzzle that an item, activity, or problem belongs to.
-
B.
hasPuzzleSolving
Indicates that an entity possesses the ability or characteristic of solving puzzles or engaging in puzzle-solving activities.
-
C.
hasMysteryType
Indicates that an entity is associated with, categorized under, or characterized by a particular type whose nature or classification is unknown, hidden, or unspecified.
-
D.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 7:33 p.m.