Triple
T36955962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enslaved: Odyssey to the West |
E914187
|
entity |
| Predicate | PCRelease |
P89646
|
FINISHED |
| Object | 2013-10-25 |
—
|
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: 2013-10-25 | Statement: [Enslaved: Odyssey to the West, PCRelease, 2013-10-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PCRelease Context triple: [Enslaved: Odyssey to the West, PCRelease, 2013-10-25]
-
A.
pcReleaseDate
chosen
Indicates the calendar date on which something becomes publicly available or is launched specifically for personal computers.
-
B.
computerSystem
Indicates a relationship where an entity functions as or is classified as a computer system, typically comprising hardware, software, and related components that operate together.
-
C.
platformFirstReleased
Indicates the date or time when a platform was initially released or made publicly available.
-
D.
usedComputerRankings
Indicates that the selection or decision was based on rankings generated by a computer system.
-
E.
introducedHardware
Indicates that an entity caused a particular piece of hardware to be brought into use or made available for the first time.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.