Triple
T37587775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | id Tech 5 |
E935166
|
entity |
| Predicate | firstReleaseGame |
P205996
|
FINISHED |
| Object | Rage |
E266305
|
NE 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: Rage | Statement: [id Tech 5, firstReleaseGame, Rage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstReleaseGame Context triple: [id Tech 5, firstReleaseGame, Rage]
-
A.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
B.
firstReleasedAs
Indicates the original title or form under which an entity (such as a work, product, or version) was initially released before any later re-releases, renamings, or editions.
-
C.
firstDeveloperRelease
Indicates the date or version when a developer-focused or pre-release version of a product was first made available.
-
D.
firstReleaseVersion
Indicates the specific version identifier associated with the initial public release of something.
-
E.
firstReleasePlatform
Indicates the platform on which something (such as a product, work, or media) was first released.
- F. None of above. chosen
Provenance (5 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40afdb36c88190b0d5ee0d61ac6459 |
completed | June 28, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.