Triple
T37576000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aragonese derby |
E934820
|
entity |
| Predicate | contestedByClubsFrom |
P183578
|
FINISHED |
| Object | Aragon region of Spain |
—
|
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: Aragon region of Spain | Statement: [Aragonese derby, contestedByClubsFrom, Aragon region of Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestedByClubsFrom Context triple: [Aragonese derby, contestedByClubsFrom, Aragon region of Spain]
-
A.
contestedByClubFrom
Indicates that a competition, match, or event is participated in or challenged by a club originating from a specified place or organization.
-
B.
contestedByClub
Indicates that a club challenges, disputes, or opposes something, such as a decision, claim, or outcome.
-
C.
leagueSupremacyContestedBy
Indicates that the dominance or top position within a league is being challenged or disputed by a particular entity.
-
D.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
E.
alsoInvolvesClubsFrom
chosen
Indicates that an event, action, or relationship includes participation or involvement of clubs originating from a specified place or region.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.