Triple
T27917808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andalusian derby |
E706120
|
entity |
| Predicate | derbyOfRegion |
P52081
|
FINISHED |
| Object | Andalusia |
—
|
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: Andalusia | Statement: [Andalusian derby, derbyOfRegion, Andalusia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derbyOfRegion Context triple: [Andalusian derby, derbyOfRegion, Andalusia]
-
A.
regionDerby
chosen
Indicates a competitive match or rivalry that takes place between teams or participants from the same geographic region.
-
B.
derby
Indicates a competitive match or contest, typically between closely linked or rival entities (such as teams from the same area or group).
-
C.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
D.
capitalCityOfRegion
Indicates that a city serves as the official capital of a specified region, functioning as its primary administrative or governmental center.
-
E.
isDerby
Indicates that a competition or match is a derby, typically involving teams or participants from the same locality or with a strong rivalry.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:54 p.m.