Triple
T20803032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InterNorth |
E512086
|
entity |
| Predicate | typeOfMerger |
P5868
|
FINISHED |
| Object | landmark corporate merger |
—
|
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: landmark corporate merger | Statement: [InterNorth, typeOfMerger, landmark corporate merger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMerger Context triple: [InterNorth, typeOfMerger, landmark corporate merger]
-
A.
mergerType
chosen
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
B.
mergerMethod
Indicates the method or process by which two or more entities are combined or merged into a single entity.
-
C.
hasMerger
Indicates a relationship where two or more entities combine into a single entity through a merger event.
-
D.
mergerImplemented
Indicates that a planned merger between entities has been fully executed and put into effect.
-
E.
mergerResult
Indicates that one or more entities have combined into a single entity, specifying the outcome or resulting entity of the merger.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2b2d5688190aaa58a2594d4787c |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:39 p.m.