Triple
T27211815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zevenaar |
E684016
|
entity |
| Predicate | hasMergerEffectiveDate |
P180607
|
FINISHED |
| Object | 2018-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: 2018-01-01 | Statement: [Zevenaar, hasMergerEffectiveDate, 2018-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMergerEffectiveDate Context triple: [Zevenaar, hasMergerEffectiveDate, 2018-01-01]
-
A.
hasMerger
Indicates a relationship where two or more entities combine into a single entity through a merger event.
-
B.
hasJurisdictionAfterMerger
Indicates that an authority or entity holds legal or regulatory jurisdiction over another entity or domain following a merger event.
-
C.
mergerPeriod
Indicates the time span during which two or more entities are in the process of merging into a single combined entity.
-
D.
hasMaturityDate
Indicates the date on which an obligation, instrument, or agreement is scheduled to become due or reach the end of its term.
-
E.
mergerImplemented
Indicates that a planned merger between entities has been fully executed and put into effect.
- F. None of above. chosen
Provenance (4 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 27, 2026, 9:39 a.m.