Triple
T38592605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barrier Projector |
E932487
|
entity |
| Predicate | teamAffect |
P126972
|
FINISHED |
| Object | Affects both Winston and allied heroes |
—
|
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: Affects both Winston and allied heroes | Statement: [Barrier Projector, teamAffect, Affects both Winston and allied heroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamAffect Context triple: [Barrier Projector, teamAffect, Affects both Winston and allied heroes]
-
A.
opponentTeamsAffected
chosen
Indicates that the specified action, condition, or effect applies to the teams designated as opponents.
-
B.
teamAction
Indicates an action that is performed collectively by a group functioning as a team.
-
C.
team1
Indicates that the referenced entity is the first team or side participating in a competitive or relational context.
-
D.
antagonisticTeam
Indicates a relationship where two teams are in active opposition or conflict with each other.
-
E.
ABAteam
Indicates a relationship where an entity is a team that competes in or is affiliated with the American Basketball Association (ABA).
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.