Triple
T36957877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doom game engine |
E914234
|
entity |
| Predicate | predecessorEngine |
P45141
|
FINISHED |
| Object | Wolfenstein 3D engine |
—
|
NE NERFINISHED |
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: Wolfenstein 3D engine | Statement: [Doom game engine, predecessorEngine, Wolfenstein 3D engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorEngine Context triple: [Doom game engine, predecessorEngine, Wolfenstein 3D engine]
-
A.
predecessorClassEngineType
Indicates that one engine type class is the predecessor of another engine type class in a sequence or hierarchy.
-
B.
predecessorModel
chosen
Indicates that one model directly precedes another in a sequence, version history, or developmental lineage.
-
C.
predecessorSystem
Indicates that one system existed or was in use before and was replaced or superseded by another system.
-
D.
predecessorVersion
Indicates that one entity is an earlier or prior version in a version sequence relative to another entity.
-
E.
predecessorService
Indicates that one service must be completed or occur before another service can begin or be considered.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:13 p.m.