Triple
T27917823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andalusian derby |
E706120
|
entity |
| Predicate | hasRivalFanGroups |
P53223
|
FINISHED |
| Object | Biris Norte |
—
|
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: Biris Norte | Statement: [Andalusian derby, hasRivalFanGroups, Biris Norte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalFanGroups Context triple: [Andalusian derby, hasRivalFanGroups, Biris Norte]
-
A.
hasFanBaseRivalry
chosen
Indicates a competitive or antagonistic relationship between the fan bases of two entities.
-
B.
hasForeignRival
Indicates that an entity has at least one rival that is based in or originates from a different country or foreign jurisdiction.
-
C.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
D.
hasRivalStand
Indicates that one entity maintains a competing or opposing stand, position, or operation in relation to another entity.
-
E.
hasLocalRivalry
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 6:54 p.m.