Triple
T11542673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quick Play |
E273710
|
entity |
| Predicate | hasMatchmaking |
P43216
|
FINISHED |
| Object | skill-based matchmaking |
—
|
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: skill-based matchmaking | Statement: [Quick Play, hasMatchmaking, skill-based matchmaking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatchmaking Context triple: [Quick Play, hasMatchmaking, skill-based matchmaking]
-
A.
hasLobby
Indicates that an entity includes or is equipped with a lobby area as part of its premises or structure.
-
B.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
C.
hasMultiplayer
chosen
Indicates that an entity (such as a game or application) supports a mode where multiple users can participate or interact simultaneously.
-
D.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
-
E.
canJoin
Indicates that one entity is permitted or able to become a member or participant in another entity or group.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e09eec8190894069d86b79183d |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.