Triple
T36957177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quake series |
E914216
|
entity |
| Predicate | engineUsed |
P56323
|
FINISHED |
| Object | id Tech 4 |
—
|
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: id Tech 4 | Statement: [Quake series, engineUsed, id Tech 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineUsed Context triple: [Quake series, engineUsed, id Tech 4]
-
A.
engineUsedIn
Indicates that a particular engine is utilized as a component or power source within a specified system, device, or application.
-
B.
engineTypeUsed
chosen
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
C.
engineName
Indicates the specific name assigned to an engine associated with an entity.
-
D.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
E.
engineTypeIncluded
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
- 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.