Triple
T23644431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wieringen |
E583989
|
entity |
| Predicate | administrativeMergeDate |
P176
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Wieringen, administrativeMergeDate, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeMergeDate Context triple: [Wieringen, administrativeMergeDate, 2012]
-
A.
administrativeChangeDate
Indicates the date on which an administrative change (such as an update, modification, or reclassification) affecting the entity was officially recorded or took effect.
-
B.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
C.
mergerYear
chosen
Indicates the year in which two or more entities formally merged into a single entity.
-
D.
timeOfMergerOrAcquisition
Indicates the specific point in time when a merger or acquisition event occurs between entities.
-
E.
incorporatedIntoOnDate
Indicates that one entity was formally incorporated into or merged with another entity on a specific 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2832d9c8190b19c55deee39eff2 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.