Triple
T27750528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Spades |
E702101
|
entity |
| Predicate | typicalPlayersPerGame |
P191665
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Internet Spades, typicalPlayersPerGame, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPlayersPerGame Context triple: [Internet Spades, typicalPlayersPerGame, 4]
-
A.
supportsPlayersPerGame
chosen
Indicates that something is compatible with or can accommodate a specified number of players in each game session.
-
B.
numberPerGame
Indicates the average count of a particular statistic or event that occurs for an entity in each game.
-
C.
pointsPerGame
Indicates the average number of points an entity scores per game over a given set of games.
-
D.
endsPerGame
Indicates the number of times something (such as a period, segment, or unit of play) concludes within a single game.
-
E.
teamCountPerGame
Indicates the number of teams that participate in a single game or match.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
Created at: April 27, 2026, 4:19 p.m.