Triple
T34032220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Saint-Étienne |
E872686
|
entity |
| Predicate | departmentCovered |
P85516
|
FINISHED |
| Object | Loire department |
—
|
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: Loire department | Statement: [Diocese of Saint-Étienne, departmentCovered, Loire department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: departmentCovered Context triple: [Diocese of Saint-Étienne, departmentCovered, Loire department]
-
A.
coversDepartment
chosen
Indicates that one entity includes, encompasses, or has responsibility for a particular department within its scope.
-
B.
departmentServed
Indicates that an entity provides service or support to a particular department.
-
C.
categoryCovered
Indicates that one category is included within, addressed by, or encompassed under the scope of another entity or context.
-
D.
workCovered
Indicates that one work or effort is included within the scope, protection, or responsibility defined by another entity or arrangement.
-
E.
department
Indicates that one entity functions as an organizational unit or division within another, typically larger, entity.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:51 a.m.