Triple
T26554453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Atlantic |
E671763
|
entity |
| Predicate | formedAsOneOf |
P50838
|
FINISHED |
| Object | Baby Bells |
—
|
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: Baby Bells | Statement: [Bell Atlantic, formedAsOneOf, Baby Bells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedAsOneOf Context triple: [Bell Atlantic, formedAsOneOf, Baby Bells]
-
A.
formedAsGroupOf
Indicates that something came into existence by being created or organized as a collection of multiple members acting together as a group.
-
B.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
C.
knownAsOneOf
chosen
Indicates that an entity is recognized or referred to as one member of a specified set of alternative names, labels, or identities.
-
D.
formedTo
Indicates that one entity was created, established, or organized for the purpose of serving, supporting, or enabling another entity or activity.
-
E.
formedTogetherWith
Indicates that two or more entities were created, established, or brought into existence at the same time or as part of the same formation process.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 27, 2026, 1:49 a.m.