Triple
T4458743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Staubach Company |
E98196
|
entity |
| Predicate | mergerOrAcquisitionType |
P7185
|
FINISHED |
| Object | corporate acquisition |
—
|
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: corporate acquisition | Statement: [The Staubach Company, mergerOrAcquisitionType, corporate acquisition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerOrAcquisitionType Context triple: [The Staubach Company, mergerOrAcquisitionType, corporate acquisition]
-
A.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
B.
acquisitionType
chosen
Indicates the specific kind or category of acquisition relationship that exists between entities (such as a company buying another company, assets, or a controlling stake).
-
C.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
-
D.
acquiredCompany
Indicates that one entity has purchased and taken ownership or control of another company.
-
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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3567184f481908a2787e4ac9bb345 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.