Triple
T24389244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riadares |
E614838
|
entity |
| Predicate | possibleRegion |
P62106
|
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: [Riadares, possibleRegion, Galicia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleRegion Context triple: [Riadares, possibleRegion, Galicia]
-
A.
likelyRegion
chosen
Indicates that an entity is probably located in, associated with, or originates from a particular geographic region.
-
B.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
-
C.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
D.
mentionsRegion
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
-
E.
formationRegion
Indicates the place or area where something originates, is created, or comes into being.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29457a0d08190ad19b55625d7a437 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:04 a.m.