Triple
T37464317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurubashi Arena |
E930995
|
entity |
| Predicate | notableForPlayers |
P205905
|
FINISHED |
| Object | world PvP achievements |
—
|
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: world PvP achievements | Statement: [Gurubashi Arena, notableForPlayers, world PvP achievements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableForPlayers Context triple: [Gurubashi Arena, notableForPlayers, world PvP achievements]
-
A.
hasNotablePlayer
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
-
B.
organNotablePlayer
Indicates that a person is a notable or distinguished player of a particular organ.
-
C.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
D.
notablePlayerInRuns
Indicates that a player is notably associated with achieving a significant number of runs, such as in a particular match, season, or competition.
-
E.
positionOfNotablePlayer
Indicates the role or playing position that a notable player occupies within a team or sport.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.