Triple
T2891824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Red Rose |
E63842
|
entity |
| Predicate | competitionRival |
P22658
|
FINISHED |
| Object | University of York sports teams |
—
|
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: University of York sports teams | Statement: [The Red Rose, competitionRival, University of York sports teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionRival Context triple: [The Red Rose, competitionRival, University of York sports teams]
-
A.
rivalOf
chosen
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
B.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
C.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
D.
competition
Indicates a relationship where two or more entities strive against each other to achieve a superior outcome, advantage, or reward.
-
E.
primaryCompetition
Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe060f49c8190bc804614a141c738 |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:07 p.m.