Triple
T36268262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halfweg |
E892289
|
entity |
| Predicate | mergerOrDissolutionDate |
P21874
|
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: [Halfweg, mergerOrDissolutionDate, 2019-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerOrDissolutionDate Context triple: [Halfweg, mergerOrDissolutionDate, 2019-01-01]
-
A.
hasDissolutionDate
Indicates the date on which an entity, such as an organization or legal arrangement, formally ceases to exist or is officially dissolved.
-
B.
demutualizationDate
Indicates the date on which a mutual organization formally converts into a non-mutual (typically shareholder-owned) entity.
-
C.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
D.
consolidationDate
chosen
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
E.
divestitureDate
Indicates the date on which an entity formally disposes of, sells, or otherwise relinquishes ownership or control of an asset, business unit, or investment.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.