Triple
T27730577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamerscore |
E697419
|
entity |
| Predicate | hasMinimumPerAchievement |
P84417
|
FINISHED |
| Object | 0 points |
—
|
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: 0 points | Statement: [Gamerscore, hasMinimumPerAchievement, 0 points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinimumPerAchievement Context triple: [Gamerscore, hasMinimumPerAchievement, 0 points]
-
A.
hasSubjectAchievement
Indicates that an entity has achieved, accomplished, or earned a particular subject-related goal, milestone, or recognition.
-
B.
hasMinimum
chosen
Indicates that an entity possesses at least a specified lower bound or smallest allowable value, quantity, or level in relation to another entity or constraint.
-
C.
hasMainAchievement
Indicates that an entity possesses a primary or most significant achievement associated with it.
-
D.
requiresMinimumScore
Indicates that one entity can only be obtained, accessed, or considered valid if another entity’s score meets or exceeds a specified minimum threshold.
-
E.
hasFounderAchievement
Indicates that an entity has received or holds a notable achievement, recognition, or award specifically in its role as a founder.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 3:11 p.m.