Triple
T19759050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Lorraine |
E474577
|
entity |
| Predicate | dateMergedIntoGrandEst |
P4318
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [French Lorraine, dateMergedIntoGrandEst, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateMergedIntoGrandEst Context triple: [French Lorraine, dateMergedIntoGrandEst, 2016]
-
A.
dateMergedIntoMontreal
Indicates that an entity’s date corresponds to when it was officially merged into the city of Montreal.
-
B.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
C.
unificationDate
chosen
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
D.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
E.
dioceseMergedInto
Indicates that one diocese has been dissolved or reorganized and incorporated into another diocese, transferring its jurisdiction and authority to the latter.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6531e79fc819094a9f88182e90dab |
completed | April 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.