Triple
T23422987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McCaw Cellular Communications |
E560713
|
entity |
| Predicate | strategicPartnerBeforeAcquisition |
P31028
|
FINISHED |
| Object | AT&T |
—
|
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: AT&T | Statement: [McCaw Cellular Communications, strategicPartnerBeforeAcquisition, AT&T]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicPartnerBeforeAcquisition Context triple: [McCaw Cellular Communications, strategicPartnerBeforeAcquisition, AT&T]
-
A.
acquisitionPartner
chosen
Indicates a relationship where one entity collaborates with or assists another in acquiring a third entity, asset, or resource.
-
B.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
-
C.
wasGoverningPartnerUnder
Indicates that one entity served as the governing partner under the authority, framework, or leadership of another entity.
-
D.
affiliationBeforeMerger
Indicates that an entity was affiliated with another entity prior to a merger event involving one or both of them.
-
E.
selectedPartner
Indicates that one entity has been chosen or designated as the partner of 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54780d88190a7d5c1426b85b7fc |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:47 p.m.