Triple
T32510611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consumer Value Store |
E830919
|
entity |
| Predicate | originalFullNameOf |
P17477
|
FINISHED |
| Object | CVS Pharmacy |
E1282937
|
NE 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: CVS Pharmacy | Statement: [Consumer Value Store, originalFullNameOf, CVS Pharmacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalFullNameOf Context triple: [Consumer Value Store, originalFullNameOf, CVS Pharmacy]
-
A.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
B.
fullLegalName
Indicates that the associated value is the complete, official legal name of the entity as recognized by law or formal records.
-
C.
originalGivenName
Indicates the personal first name that an individual was originally given at birth or naming, before any later changes.
-
D.
namesakeFullName
chosen
Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
-
E.
fullGivenNameOf
Indicates that one entity is the complete, formal given name corresponding to another entity (such as a person or identifier).
- F. None of above.
Provenance (4 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01b130f6808190b86442fb16930e6e |
completed | May 11, 2026, 10:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34bcd6ba8c81908b53111c4ad1e2ed |
completed | June 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_6a01b023157881909a802e06eced3e2f |
completed | May 11, 2026, 10:32 a.m. |
Created at: May 1, 2026, 1 a.m.