Triple
T36342733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Boyd |
E894973
|
entity |
| Predicate | antagonisticTeam |
P185144
|
FINISHED |
| Object | New York Yankees |
—
|
NE NERFINISHED |
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: New York Yankees | Statement: [Joe Boyd, antagonisticTeam, New York Yankees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antagonisticTeam Context triple: [Joe Boyd, antagonisticTeam, New York Yankees]
-
A.
rivalTeam
Indicates that one team is in a competitive or adversarial relationship with another team, often vying for superiority or dominance.
-
B.
teamOpposed
Indicates that one team is in opposition or conflict with another team, such as being rivals or competing against each other.
-
C.
opponentGroup
Indicates that one group is in opposition or conflict with another group, typically as a rival, competitor, or adversary.
-
D.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
E.
teamOpponent
Indicates that two teams are competing against each other as opponents in a game or match.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bb3f23f48190b0b9c2d667e09b52 |
completed | May 3, 2026, 9:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.