Triple
T26839772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saraperos de Saltillo |
E675744
|
entity |
| Predicate | hasTypeOfRivalry |
P146762
|
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: [Saraperos de Saltillo, hasTypeOfRivalry, regional rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfRivalry Context triple: [Saraperos de Saltillo, hasTypeOfRivalry, regional rivalry]
-
A.
typeOfRivalry
Indicates a competitive or adversarial relationship between entities, specifying the particular kind or nature of rivalry that exists between them.
-
B.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
C.
hasRivalryCategory
chosen
Indicates that there exists a competitive or adversarial relationship between entities that falls into a specific classified type or category of rivalry.
-
D.
hasRivalryContext
Indicates that there exists a competitive or adversarial relationship between entities within a specific situational or contextual framework.
-
E.
hasSubRivalryContext
Indicates that one rivalry context is a more specific, subordinate part of a broader rivalry context within the same overall competitive relationship.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 5:07 a.m.