Triple
T30425534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arroyomolinos de la Vera |
E774016
|
entity |
| Predicate | locatedInRegionOfSpain |
P99815
|
FINISHED |
| Object | Extremadura |
—
|
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: Extremadura | Statement: [Arroyomolinos de la Vera, locatedInRegionOfSpain, Extremadura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInRegionOfSpain Context triple: [Arroyomolinos de la Vera, locatedInRegionOfSpain, Extremadura]
-
A.
isInNorthernSpain
Indicates that something is located within the geographical region of northern Spain.
-
B.
mainRegionInSpain
Indicates that a location is the primary or most significant region associated with a place or entity within Spain.
-
C.
hasIberianLocation
Indicates that something is located in, or geographically associated with, the Iberian Peninsula.
-
D.
otherDOCaRegionInSpain
Indicates that one document is about a region located in Spain, while the other document concerns a different region within Spain.
-
E.
inAutonomousCommunity
chosen
Indicates that one entity is located within or belongs administratively to a specific autonomous community.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00bb3a6f888190b3ecd0fbc9af9b4a |
completed | May 10, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_6a00b902dbf881909e098ff102b7ea7e |
completed | May 10, 2026, 4:57 p.m. |
Created at: April 29, 2026, 8:06 p.m.