Triple
T27730578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamerscore |
E697419
|
entity |
| Predicate | hasCommonPerAchievementValue |
P199411
|
FINISHED |
| Object | 5 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: 5 points | Statement: [Gamerscore, hasCommonPerAchievementValue, 5 points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonPerAchievementValue Context triple: [Gamerscore, hasCommonPerAchievementValue, 5 points]
-
A.
hasAchievements
Indicates that an entity possesses or is associated with one or more notable accomplishments, awards, or completed goals.
-
B.
hasAchievementType
Indicates that an achievement is classified under a specific type or category of achievement.
-
C.
hasSubjectAchievement
Indicates that an entity has achieved, accomplished, or earned a particular subject-related goal, milestone, or recognition.
-
D.
hasRelatedTrophy
Indicates that there exists a trophy that is associated with, linked to, or relevant to the given entity.
-
E.
associatedAchievement
Indicates a relationship where one entity is linked to, or recognized in connection with, a particular achievement.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
| PDg | Predicate description generation | batch_69ff38b8843c819097359a4d77e9d442 |
completed | May 9, 2026, 1:38 p.m. |
Created at: April 27, 2026, 3:11 p.m.