Triple
T23201228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warhammer tabletop gaming |
E580016
|
entity |
| Predicate | hasPlayMode |
P101458
|
FINISHED |
| Object | matched play |
—
|
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: matched play | Statement: [Warhammer tabletop gaming, hasPlayMode, matched play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayMode Context triple: [Warhammer tabletop gaming, hasPlayMode, matched play]
-
A.
hasPlayPattern
Indicates a characteristic way or style in which an entity typically plays, behaves, or performs an activity.
-
B.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
-
C.
playableMode
Indicates that a particular mode, configuration, or state can be actively used or played within a system or application.
-
D.
hasPlayFormat
chosen
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
-
E.
hasPlaySource
Indicates that something derives its performance, playback, or execution from a specified source.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f19079c44881909e8677921b08b931 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:06 p.m.