Triple
T14186656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binnenmaas |
E351594
|
entity |
| Predicate | mergedIntoOnDate |
P50534
|
FINISHED |
| Object | 2019-01-01 |
—
|
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: 2019-01-01 | Statement: [Binnenmaas, mergedIntoOnDate, 2019-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedIntoOnDate Context triple: [Binnenmaas, mergedIntoOnDate, 2019-01-01]
-
A.
mergedInto
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
B.
incorporatedIntoOnDate
chosen
Indicates that one entity was formally incorporated into or merged with another entity on a specific date.
-
C.
integrationDate
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.
integratedDate
Indicates the date on which one entity was incorporated, combined, or brought into a larger system or whole.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61cd5778819092a03597bcdcc182 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:03 a.m.