Triple
T9910762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | local parish church of Sant Pere |
E185134
|
entity |
| Predicate | parishFor |
P71075
|
FINISHED |
| Object | town of Santpedor |
—
|
LITERAL FINISHED |
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: town of Santpedor | Statement: [local parish church of Sant Pere, parishFor, town of Santpedor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishFor Context triple: [local parish church of Sant Pere, parishFor, town of Santpedor]
-
A.
parish
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
-
B.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
C.
parishWith
chosen
Indicates that one entity is associated with, belongs to, or is administered together with another entity as part of the same parish.
-
D.
civilParishFor
Indicates that one entity is the civil parish to which another entity (such as a place or administrative area) belongs or is assigned.
-
E.
parishesIncluded
Indicates that certain parishes are contained within, or form part of, a larger administrative, geographic, or organizational unit.
- 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb512a26881908eb72a21ffb1efef |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:41 p.m.