Triple
T25942653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boavista F.C. |
E653747
|
entity |
| Predicate | traditionalRivals |
P74502
|
FINISHED |
| Object | FC Porto |
—
|
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: FC Porto | Statement: [Boavista F.C., traditionalRivals, FC Porto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalRivals Context triple: [Boavista F.C., traditionalRivals, FC Porto]
-
A.
associatedRivalry
chosen
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
B.
conferenceRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same conference or organized grouping.
-
C.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
D.
nicknameOfRivalryBetween
Indicates that one entity is a nickname or informal title used to refer to a particular rivalry between other entities.
-
E.
rivalOf
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 22, 2026, 8:41 a.m.