Triple
T38174376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derbi Valenciano |
E1000164
|
entity |
| Predicate | hasLocalRivalriesWith |
P18267
|
FINISHED |
| Object | Alicante-based clubs |
—
|
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: Alicante-based clubs | Statement: [Derbi Valenciano, hasLocalRivalriesWith, Alicante-based clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalRivalriesWith Context triple: [Derbi Valenciano, hasLocalRivalriesWith, Alicante-based clubs]
-
A.
hasLocalRivalry
chosen
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
-
B.
hasRivalryIn
Indicates that two entities are in a state of competition or opposition within a specific domain, context, or field.
-
C.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
D.
hasNationalRivalry
Indicates that there is a notable, often historically rooted competitive or adversarial relationship between two nations.
-
E.
hasLocalRivalryVenueWith
Indicates that two entities share a venue or location where a local rivalry between them is regularly contested or expressed.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: May 3, 2026, 4:29 p.m.