Triple
T1120177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Board of Trade |
E11191
|
entity |
| Predicate | mergerCompletedIn |
P176
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Chicago Board of Trade, mergerCompletedIn, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerCompletedIn Context triple: [Chicago Board of Trade, mergerCompletedIn, 2007]
-
A.
mergerResult
Indicates that one or more entities have combined into a single entity, specifying the outcome or resulting entity of the merger.
-
B.
mergerSettlement
Indicates a legal or financial resolution reached between parties involved in a merger, typically settling disputes or claims arising from the merger transaction.
-
C.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
D.
mergerYear
chosen
Indicates the year in which two or more entities formally merged into a single entity.
-
E.
dissolvedByMerger
Indicates that an entity ceased to exist as an independent entity because it was legally combined into another entity through a 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4562f48190831e959f5f309956 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.