Triple
T27972585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Lepra |
E706402
|
entity |
| Predicate | rivalNickname |
P164548
|
FINISHED |
| Object | Canalla |
—
|
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: Canalla | Statement: [La Lepra, rivalNickname, Canalla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalNickname Context triple: [La Lepra, rivalNickname, Canalla]
-
A.
contrastsWithRivalNickname
Indicates that one nickname is intentionally different from and set in opposition to a rival nickname.
-
B.
rivalOf
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
C.
rivalTeam
Indicates that one team is in a competitive or adversarial relationship with another team, often vying for superiority or dominance.
-
D.
rivalryName
Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
-
E.
rivalTeamAbbreviation
Indicates that one team is identified as the rival of another team, using the rival team's standard abbreviation.
- F. None of above. chosen
Provenance (4 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 7:39 p.m.