Triple
T33542001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sèvremoine |
E859094
|
entity |
| Predicate | effectiveDateOfMerger |
P180607
|
FINISHED |
| Object | 2015-12-15 |
—
|
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: 2015-12-15 | Statement: [Sèvremoine, effectiveDateOfMerger, 2015-12-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveDateOfMerger Context triple: [Sèvremoine, effectiveDateOfMerger, 2015-12-15]
-
A.
hasMergerEffectiveDate
chosen
Indicates the date on which a merger between entities becomes legally effective and operational.
-
B.
timeOfMergerOrAcquisition
Indicates the specific point in time when a merger or acquisition event occurs between entities.
-
C.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
D.
mergerPeriod
Indicates the time span during which two or more entities are in the process of merging into a single combined entity.
-
E.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 1:39 a.m.