Triple
T27731936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unity Multiplayer services |
E697449
|
entity |
| Predicate | supportsGameType |
P10208
|
FINISHED |
| Object | real-time multiplayer game |
—
|
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: real-time multiplayer game | Statement: [Unity Multiplayer services, supportsGameType, real-time multiplayer game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGameType Context triple: [Unity Multiplayer services, supportsGameType, real-time multiplayer game]
-
A.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
B.
includesGameType
chosen
Indicates that one entity contains or supports a particular type or category of game.
-
C.
supportsGames
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
D.
supportsGameStyle
Indicates that one entity is compatible with or able to accommodate a particular game style or mode of play.
-
E.
usedForGameType
Indicates that something is utilized or designated for a particular type or category of game.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: April 27, 2026, 3:12 p.m.