Triple
T5076926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anjou |
E114419
|
entity |
| Predicate | mergeEffectiveDate |
P6972
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Anjou, mergeEffectiveDate, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergeEffectiveDate Context triple: [Anjou, mergeEffectiveDate, 2002]
-
A.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
B.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
C.
integrationDate
chosen
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
D.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
E.
updatedSpecificationDate
Indicates the date on which a specification was last revised or brought up to date.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d3b0088190a658864cb120eef4 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.