Triple
T1010958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwight Fairfield |
E21820
|
entity |
| Predicate | playableInMode |
P11331
|
FINISHED |
| Object | online multiplayer |
—
|
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: online multiplayer | Statement: [Dwight Fairfield, playableInMode, online multiplayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableInMode Context triple: [Dwight Fairfield, playableInMode, online multiplayer]
-
A.
playsOnSurface
Indicates that an entity performs or engages in an activity while being in contact with or supported by a particular surface.
-
B.
playsOn
Indicates that one entity participates or performs on a particular team, platform, or medium.
-
C.
usedOnMode
chosen
Indicates that something is applied, operated, or functions specifically in a given mode or operational setting.
-
D.
isPlayedIn
Indicates that an instance of a game, sport, or performance takes place within or is hosted at a particular location or venue.
-
E.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b7203124819091de68cba5f731c1 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.