Triple
T27790742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIT |
E701071
|
entity |
| Predicate | exchangeListingFor |
P27066
|
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, exchangeListingFor, Ameritech Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeListingFor Context triple: [AIT, exchangeListingFor, Ameritech Corporation]
-
A.
exchangeListingStatus
Indicates the status or change in status of an entity’s listing on an exchange (e.g., listed, delisted, suspended, or pending).
-
B.
exchangeType
Indicates the kind or category of exchange occurring between entities, such as the method, direction, or nature of what is being traded or transferred.
-
C.
exchangeSegmentOf
Indicates that one entity gives a portion or segment of something to another entity, typically as part of a reciprocal transfer or trade.
-
D.
exchangeSegment
Indicates a relationship where one entity trades or swaps a defined portion or segment of something with another entity.
-
E.
exchangedFor
chosen
Indicates that one entity has been traded or substituted in return for another entity.
- 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_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. |
Created at: April 27, 2026, 5:28 p.m.