Triple
T29366524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Club Irapuato |
E744733
|
entity |
| Predicate | rivalryTypeWithClubLeón |
P74502
|
FINISHED |
| Object | regional rivalry |
—
|
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: regional rivalry | Statement: [Club Irapuato, rivalryTypeWithClubLeón, regional rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryTypeWithClubLeón Context triple: [Club Irapuato, rivalryTypeWithClubLeón, regional rivalry]
-
A.
associatedRivalry
chosen
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
B.
rivalClubsInSameCity
Indicates that two sports clubs are rivals and are based in the same city.
-
C.
countryRivalClubs
Indicates that two sports clubs from the same country are considered rivals.
-
D.
rivalryInvolvesCity
Indicates that a rivalry relationship includes or is associated with a particular city as one of its involved locations.
-
E.
rivalLeague
Indicates that two leagues are in competition with each other, typically vying for similar audiences, resources, or status.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6698c5fd481909062bf8e7057dd61 |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:23 p.m.