Triple
T28993521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limavady United F.C. |
E736092
|
entity |
| Predicate | rivalryWithClubFrom |
P22658
|
FINISHED |
| Object | Coleraine |
—
|
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: Coleraine | Statement: [Limavady United F.C., rivalryWithClubFrom, Coleraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryWithClubFrom Context triple: [Limavady United F.C., rivalryWithClubFrom, Coleraine]
-
A.
rivalClubsInSameCity
Indicates that two sports clubs are rivals and are based in the same city.
-
B.
countryRivalClubs
Indicates that two sports clubs from the same country are considered rivals.
-
C.
rivalOf
chosen
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
D.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
E.
foundedAsRivalOf
Indicates that an entity was established specifically to compete with or challenge another entity.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7f067081909057e9c6e1fd0bdd |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:28 a.m.