Triple
T14335877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaqueri "Aphromoo" Black |
E355464
|
entity |
| Predicate | gameRoleSpecialty |
P100060
|
FINISHED |
| Object | engage supports |
—
|
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: engage supports | Statement: [Zaqueri "Aphromoo" Black, gameRoleSpecialty, engage supports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameRoleSpecialty Context triple: [Zaqueri "Aphromoo" Black, gameRoleSpecialty, engage supports]
-
A.
teamSpecialty
Indicates the particular area of expertise or focus that characterizes a team’s skills or activities.
-
B.
gameRoleForPlayers
chosen
Indicates the specific role or function that players have within a particular game or gameplay context.
-
C.
specialRole
Indicates that an entity holds a distinctive or exceptional function, status, or responsibility in relation to another entity or context.
-
D.
lineupRole
Indicates the specific role or position an entity holds within a lineup or ordered group.
-
E.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c20d2148190bb534bef338e871d |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.