Triple
T8619836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monkey Island 2: LeChuck's Revenge |
E204134
|
entity |
| Predicate | specialEditionReleaseYear |
P16584
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Monkey Island 2: LeChuck's Revenge, specialEditionReleaseYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialEditionReleaseYear Context triple: [Monkey Island 2: LeChuck's Revenge, specialEditionReleaseYear, 2010]
-
A.
anniversaryEditionPublicationYear
Indicates the year in which an anniversary edition of a work was published.
-
B.
expandedEditionYear
chosen
Indicates the year in which a work’s expanded or enlarged edition was published or released.
-
C.
notableEditionYear
Indicates the year in which a particular edition of something (such as a work, product, or publication) is considered notable or significant.
-
D.
specialEdition
Indicates that an item is a distinct, limited, or enhanced version of a standard release, often with unique features, packaging, or content.
-
E.
correctedEditionYear
Indicates the year in which a corrected or revised edition of a work was published or released.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc471458f48190a6d8858f8074727d |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.