Triple
T21627266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M.U.L.E. |
E533734
|
entity |
| Predicate | supportsHotseatPlay |
P40438
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [M.U.L.E., supportsHotseatPlay, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHotseatPlay Context triple: [M.U.L.E., supportsHotseatPlay, true]
-
A.
supportsRemotePlay
Indicates that one entity enables or is compatible with remote play functionality for another entity.
-
B.
supportsInstantPlay
Indicates that one entity enables or is compatible with immediate, on-demand use or playback of another entity without requiring prior download or installation.
-
C.
supportsSeatedExperience
Indicates that one entity enables, accommodates, or is suitable for another entity to be used or experienced while seated.
-
D.
supportsLocalMultiplayer
chosen
Indicates that the subject provides functionality for multiple players to play together on the same device or local network.
-
E.
supportsGameStreaming
Indicates that one entity provides the capability for another entity to stream and play games remotely in real time.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52141e1c8190a861f4bc7cfcb490 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.