Triple
T8562511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totally Games |
E202721
|
entity |
| Predicate | gameEngineFocus |
P31
|
FINISHED |
| Object | space flight and combat mechanics |
—
|
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: space flight and combat mechanics | Statement: [Totally Games, gameEngineFocus, space flight and combat mechanics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameEngineFocus Context triple: [Totally Games, gameEngineFocus, space flight and combat mechanics]
-
A.
gameEngine
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.
homeGamesFocus
Indicates a focus or emphasis on games played at a team's home venue rather than away or neutral-site games.
-
C.
gameContext
Indicates the situational framework or environment in which a game’s actions, rules, and interactions take place.
-
D.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
E.
stateOfFocus
Indicates the particular subject, area, or activity that an entity is currently concentrating attention or effort on.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe94c0c3c8190aca981c07b090dc0 |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.