Triple
T8286229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solitaire |
E193792
|
entity |
| Predicate | isPerfectInformationGame |
P82529
|
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: [Solitaire, isPerfectInformationGame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPerfectInformationGame Context triple: [Solitaire, isPerfectInformationGame, true]
-
A.
isPerfect
Indicates that an entity possesses all required qualities or characteristics to the highest or complete degree, without flaws or deficiencies.
-
B.
hasTieGame
Indicates that a game or match has ended with both sides having the same score, resulting in no winner.
-
C.
inningsPlayed
Indicates the number of innings in which an entity (typically a player or team) has participated during a game or season.
-
D.
isTotallyPerfect
Indicates that an entity possesses complete flawlessness or ideal qualities in every relevant aspect.
-
E.
misèreRule
Indicates that the outcome or winning condition of a game or situation is determined using misère rules, where the usual notion of winning and losing is reversed (typically making the player who would normally win instead lose).
- F. None of above. chosen
Provenance (4 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad3722481908076508908d18621 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.