Triple
T35394586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papa |
E1023036
|
entity |
| Predicate | hasPlayableStatus |
P191134
|
FINISHED |
| Object | playable in single-player mode |
—
|
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: playable in single-player mode | Statement: [Papa, hasPlayableStatus, playable in single-player mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayableStatus Context triple: [Papa, hasPlayableStatus, playable in single-player mode]
-
A.
playableStatus
chosen
Indicates whether an entity (such as a media item, game, or track) is currently able to be played or accessed for playback.
-
B.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
C.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
D.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
E.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 3, 2026, 4:03 p.m.