Triple
T30753494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asamblea de Extremadura |
E783017
|
entity |
| Predicate | capitalOfRegionSeat |
P85786
|
FINISHED |
| Object | Mérida |
—
|
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: Mérida | Statement: [Asamblea de Extremadura, capitalOfRegionSeat, Mérida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfRegionSeat Context triple: [Asamblea de Extremadura, capitalOfRegionSeat, Mérida]
-
A.
capitalCityOfRegion
Indicates that a city serves as the official capital of a specified region, functioning as its primary administrative or governmental center.
-
B.
capitalOfReferencedRegion
chosen
Indicates that one entity serves as the capital city or administrative center of the region referenced by another entity.
-
C.
capitalOfRegionLocatedHere
Indicates that a place serves as the capital of a region that is geographically located at or associated with this place.
-
D.
capitalOfRegionContext
Indicates that a location serves as the capital city or administrative center within the context of a specific region.
-
E.
capitalLocatedInRegion
Indicates that a capital city is geographically situated within a specific 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 29, 2026, 8:39 p.m.