Triple
T29120191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Escape!" |
E737157
|
entity |
| Predicate | includedInCollectionYear |
P40626
|
FINISHED |
| Object | 1950 (I, Robot) |
—
|
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: 1950 (I, Robot) | Statement: ["Escape!", includedInCollectionYear, 1950 (I, Robot)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInCollectionYear Context triple: ["Escape!", includedInCollectionYear, 1950 (I, Robot)]
-
A.
endedInYear
Indicates that an event, state, or relationship concluded in the specified calendar year.
-
B.
catalogueInclusionYear
chosen
Indicates the year in which an item was first included or recorded in a catalogue.
-
C.
releaseIncludedInYearBestLists
Indicates that a particular release has been selected for inclusion in one or more "best of the year" lists.
-
D.
featuredInYear
Indicates that something was prominently presented, highlighted, or showcased during a specific calendar year.
-
E.
playedInYear
Indicates that an entity participated in or was active in a particular activity, event, or role during a specified calendar year.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: April 28, 2026, 11:25 a.m.