Triple
T29101149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sports Interactive |
E736641
|
entity |
| Predicate | hasGameEngineType |
P166659
|
FINISHED |
| Object | sports management simulation engine |
—
|
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: sports management simulation engine | Statement: [Sports Interactive, hasGameEngineType, sports management simulation engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameEngineType Context triple: [Sports Interactive, hasGameEngineType, sports management simulation engine]
-
A.
gameEngineType
chosen
Indicates the type or category of game engine associated with or used by an entity.
-
B.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
-
C.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
D.
hasEngineTypeOnDisplay
Indicates that a particular type of engine is being shown or presented as part of a display or exhibition.
-
E.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 11:12 a.m.