Triple
T34549688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Cruz de Bezana |
E887027
|
entity |
| Predicate | hasParishOrLocality |
P178050
|
FINISHED |
| Object | Bezana |
—
|
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: Bezana | Statement: [Santa Cruz de Bezana, hasParishOrLocality, Bezana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishOrLocality Context triple: [Santa Cruz de Bezana, hasParishOrLocality, Bezana]
-
A.
hasParishLevel
Indicates that an entity is associated with or classified according to a specific parish-level administrative or ecclesiastical unit.
-
B.
hasCivilParishComponent
chosen
Indicates that an entity includes or is composed of the specified civil parish as one of its administrative components.
-
C.
isParishEquivalent
Indicates that one administrative or ecclesiastical unit is considered equivalent in status or function to a parish.
-
D.
hasParishSeatNearby
Indicates that a parish has its administrative seat located in close geographic proximity to the referenced place or entity.
-
E.
hasParishJurisdiction
Indicates that one entity holds official parish-level authority or administrative control over another entity or area.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
Created at: May 1, 2026, 2:02 a.m.