Triple
T32963472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumbres |
E843302
|
entity |
| Predicate | churchOfSaintSulpiceDate |
P175442
|
FINISHED |
| Object | nineteenth century |
—
|
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: nineteenth century | Statement: [Lumbres, churchOfSaintSulpiceDate, nineteenth century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchOfSaintSulpiceDate Context triple: [Lumbres, churchOfSaintSulpiceDate, nineteenth century]
-
A.
cathedralDedication
Indicates the religious figure, event, or concept to which a cathedral is formally dedicated.
-
B.
coCathedralName
Indicates the name assigned to a church that holds the status of a co-cathedral within a diocese or ecclesiastical jurisdiction.
-
C.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
-
D.
coCathedralDedication
Indicates that a co-cathedral is formally dedicated to or in honor of a particular figure, event, or sacred concept.
-
E.
coCathedral
Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
- F. None of above. chosen
Provenance (4 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: May 1, 2026, 1:21 a.m.