Triple
T20142769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ¡Uno! |
E491215
|
entity |
| Predicate | supportsPlayerCount |
P43216
|
FINISHED |
| Object | 2 or more players |
—
|
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: 2 or more players | Statement: [¡Uno!, supportsPlayerCount, 2 or more players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPlayerCount Context triple: [¡Uno!, supportsPlayerCount, 2 or more players]
-
A.
hasPlayerCount
Indicates the number of players associated with or participating in a given entity or activity.
-
B.
supportsPlayers
Indicates that an entity provides compatibility or functionality for one or more players to participate or be used.
-
C.
maximumPlayerCount
Indicates the largest number of players that can participate at the same time in the related context or activity.
-
D.
supportsPlayer
Indicates that one entity provides assistance, resources, or backing to a player in achieving their goals or performing actions.
-
E.
hasMultiplayer
chosen
Indicates that an entity (such as a game or application) supports a mode where multiple users can participate or interact simultaneously.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679bcf2c8190ac6e969178d8acde |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.