Triple
T31901605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Metz |
E814436
|
entity |
| Predicate | recognizedAnnexationYear |
P9430
|
FINISHED |
| Object | 1648 |
—
|
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: 1648 | Statement: [Diocese of Metz, recognizedAnnexationYear, 1648]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAnnexationYear Context triple: [Diocese of Metz, recognizedAnnexationYear, 1648]
-
A.
annexedInYear
chosen
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
-
B.
annexationDate
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
-
C.
laterAnnexedTo
Indicates that one entity was annexed by another entity at a later point in time, after its initial status or affiliation.
-
D.
annexedDuring
Indicates that one entity was formally incorporated into and brought under the control of another entity during a specified time period.
-
E.
annexationStatus
Indicates the current state or condition of one territory being formally incorporated into another sovereign 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 30, 2026, 11:59 p.m.