Triple
T31901606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Metz |
E814436
|
entity |
| Predicate | concordatStatus |
P172713
|
FINISHED |
| Object | Concordat diocese |
—
|
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: Concordat diocese | Statement: [Diocese of Metz, concordatStatus, Concordat diocese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concordatStatus Context triple: [Diocese of Metz, concordatStatus, Concordat diocese]
-
A.
conciliarStatus
Indicates the formal standing or recognition of a council or conciliar decision within a broader institutional or doctrinal framework.
-
B.
covenantStatus
Indicates the current state or condition of a covenant or binding agreement between parties.
-
C.
contractStatus
Indicates the current state or phase of a contract within its lifecycle (e.g., draft, active, suspended, or terminated).
-
D.
treatyStatus
Indicates the current legal or diplomatic condition of a treaty between parties, such as whether it is proposed, signed, ratified, active, suspended, or terminated.
-
E.
concordatPartner
Indicates that two entities are formally bound by a concordat or comparable agreement defining mutual rights, obligations, or cooperation.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b168342481909e2e0d4fd99378d6 |
completed | May 3, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:59 p.m.