Triple
T997212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patrick Roy |
E21520
|
entity |
| Predicate | shootsAgainst |
P21711
|
FINISHED |
| Object | right-handed shooters |
—
|
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: right-handed shooters | Statement: [Patrick Roy, shootsAgainst, right-handed shooters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shootsAgainst Context triple: [Patrick Roy, shootsAgainst, right-handed shooters]
-
A.
shoots
Indicates that one entity propels a projectile or discharge toward another entity, typically with the intent to hit or affect it.
-
B.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
C.
archenemyOf
Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
-
D.
fightingOutOf
Indicates that an individual is competing or representing themselves in a fight or match while being officially associated with a particular location, camp, or organization.
-
E.
belligerentAgainst
Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4e0f0d081908b888c246d001786 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2af071c819086c374a16307dfe0 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b30efd2c8190b780a6dee086d0aa |
completed | March 1, 2026, 9:43 p.m. |
Created at: March 1, 2026, 7:41 p.m.