Triple
T9029097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GTE Florida |
E216122
|
entity |
| Predicate | mergerEvent |
P6600
|
FINISHED |
| Object | merger of GTE and Bell Atlantic |
—
|
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: merger of GTE and Bell Atlantic | Statement: [GTE Florida, mergerEvent, merger of GTE and Bell Atlantic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerEvent Context triple: [GTE Florida, mergerEvent, merger of GTE and Bell Atlantic]
-
A.
mergerResultedIn
Indicates that a merger between entities led to the creation, change, or outcome represented by the related entity or state.
-
B.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
C.
mergerResult
Indicates that one or more entities have combined into a single entity, specifying the outcome or resulting entity of the merger.
-
D.
mergerPartner
chosen
Indicates that two entities are involved as counterparties in a merger transaction with each other.
-
E.
mergerSettlement
Indicates a legal or financial resolution reached between parties involved in a merger, typically settling disputes or claims arising from the merger transaction.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.