Triple
T36957898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doom game engine |
E914234
|
entity |
| Predicate | graphicsLimitation |
P99
|
FINISHED |
| Object | no looking up and down in original implementation |
—
|
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: no looking up and down in original implementation | Statement: [Doom game engine, graphicsLimitation, no looking up and down in original implementation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphicsLimitation Context triple: [Doom game engine, graphicsLimitation, no looking up and down in original implementation]
-
A.
showsLimitationOf
Indicates that one entity reveals, demonstrates, or makes apparent the limitations, weaknesses, or constraints of another entity.
-
B.
viewingLimit
Indicates a restriction on how many times or for how long something can be viewed.
-
C.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
D.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
-
E.
reasonForPerformanceLimitation
Indicates that one factor serves as the cause or explanation for why a performance limitation occurs.
- 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_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.