Triple
T27790744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIT |
E701071
|
entity |
| Predicate | preAcquisitionTickerOf |
P163357
|
FINISHED |
| Object | Ameritech Corporation |
—
|
NE NERFINISHED |
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: Ameritech Corporation | Statement: [AIT, preAcquisitionTickerOf, Ameritech Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preAcquisitionTickerOf Context triple: [AIT, preAcquisitionTickerOf, Ameritech Corporation]
-
A.
acquiringCompanyTicker
Indicates the stock ticker symbol of the company that is acquiring another company in a transaction.
-
B.
succeededByTicker
Indicates that one entity is directly followed or replaced by another entity in a sequence of ticker symbols.
-
C.
tickerFor
Indicates that one entity is the stock ticker symbol used to uniquely identify another entity (typically a publicly traded company or security) in financial markets.
-
D.
afterAcquisitionBy
Indicates that something occurs or holds true following the acquisition of one entity by another.
-
E.
wasAcquiredIn
Indicates that one entity obtained ownership or control of another entity through an acquisition event that occurred at a specific time or in a specific transaction.
- F. None of above. chosen
Provenance (4 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63807606881908a3ae90fa219eebb |
completed | May 2, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 5:28 p.m.