Triple
T26554461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Atlantic |
E671763
|
entity |
| Predicate | brandLaterUsedIn |
P23474
|
FINISHED |
| Object | Bell Atlantic Yellow Pages |
—
|
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: Bell Atlantic Yellow Pages | Statement: [Bell Atlantic, brandLaterUsedIn, Bell Atlantic Yellow Pages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandLaterUsedIn Context triple: [Bell Atlantic, brandLaterUsedIn, Bell Atlantic Yellow Pages]
-
A.
brandNameUsedIn
Indicates that a particular brand name is used or appears within a specified context, such as a product, document, or communication.
-
B.
brandUsage
chosen
Indicates that one entity uses, features, or is associated with another entity’s brand in its products, services, or communications.
-
C.
brandIncorporatedInto
Indicates that one brand has been merged into, absorbed by, or otherwise formally integrated as part of another brand.
-
D.
namedBrandAfter
Indicates that one brand has been given a name derived from or in honor of another entity.
-
E.
usedBrand
Indicates that an entity has utilized, applied, or operated a particular brand in some 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 1:49 a.m.