Triple
T552306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Electric |
E11865
|
entity |
| Predicate | regulatoryEvent |
P9662
|
FINISHED |
| Object | subject to U.S. antitrust actions against AT&T |
—
|
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: subject to U.S. antitrust actions against AT&T | Statement: [Western Electric, regulatoryEvent, subject to U.S. antitrust actions against AT&T]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryEvent Context triple: [Western Electric, regulatoryEvent, subject to U.S. antitrust actions against AT&T]
-
A.
regulatoryOutcome
chosen
Indicates the result or consequence of a regulatory process, such as approval, rejection, modification, or other formal decision made by a regulatory authority regarding an entity or action.
-
B.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
C.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
D.
formationEvent
Indicates the event or process through which something comes into existence, is created, or is initially established.
-
E.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499047bd4819089ca8345f1b6e46c |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bae210819093c2e0d33a8ca51a |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.