Triple
T35472264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Río Miño |
E1025233
|
entity |
| Predicate | borderRegionSpain |
P12818
|
FINISHED |
| Object | Galicia |
—
|
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: Galicia | Statement: [Río Miño, borderRegionSpain, Galicia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRegionSpain Context triple: [Río Miño, borderRegionSpain, Galicia]
-
A.
borderTypeWithSpain
Indicates the type or nature of the border that an entity shares with Spain.
-
B.
mainRegionInSpain
Indicates that a location is the primary or most significant region associated with a place or entity within Spain.
-
C.
borderRegion
chosen
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
otherDOCaRegionInSpain
Indicates that one document is about a region located in Spain, while the other document concerns a different region within Spain.
-
E.
borderTypeWithGibraltar
Indicates the specific type or nature of the border relationship that an entity has with Gibraltar.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: May 3, 2026, 4:04 p.m.