Triple
T294788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Cowboys–Philadelphia Eagles rivalry |
E6068
|
entity |
| Predicate | team2FanReputation |
P897
|
FINISHED |
| Object | passionate and hostile toward rivals |
—
|
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: passionate and hostile toward rivals | Statement: [Dallas Cowboys–Philadelphia Eagles rivalry, team2FanReputation, passionate and hostile toward rivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team2FanReputation Context triple: [Dallas Cowboys–Philadelphia Eagles rivalry, team2FanReputation, passionate and hostile toward rivals]
-
A.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
B.
fanBase
chosen
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
C.
team2Franchise
Indicates a relationship where a second team is associated with, or belongs to, a particular franchise.
-
D.
team1Franchise
Indicates that an entity serves as or represents the franchise associated with the first team in a given sports or competitive context.
-
E.
teamName
Indicates the relationship that assigns or associates a specific name with a particular team.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e273f88190ac5355d1310376ed |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9368894819093eeae4347dfcc5a |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.