Triple
T2875307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZeniMax Online Studios |
E56863
|
entity |
| Predicate | usesGameEngine |
P26587
|
FINISHED |
| Object | Megaserver technology |
—
|
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: Megaserver technology | Statement: [ZeniMax Online Studios, usesGameEngine, Megaserver technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGameEngine Context triple: [ZeniMax Online Studios, usesGameEngine, Megaserver technology]
-
A.
gameEngine
chosen
Indicates that one entity serves as the game engine or core runtime system used to develop, run, or power another entity (such as a game or interactive application).
-
B.
hasEngineProgram
Indicates that an entity is associated with or participates in a specific engine-related program.
-
C.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
D.
typicalEngine
Indicates that an entity is the standard or commonly used engine for another entity (such as a vehicle, device, or system).
-
E.
includesDisplayEngine
Indicates that one entity contains or incorporates another entity that functions as a display engine.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe004a64481908f1897d9054a7368 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.