Triple
T30150766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Sassoon |
E766388
|
entity |
| Predicate | ownedCompany |
P169359
|
FINISHED |
| Object | E. D. Sassoon & Co. |
—
|
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: E. D. Sassoon & Co. | Statement: [Victor Sassoon, ownedCompany, E. D. Sassoon & Co.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedCompany Context triple: [Victor Sassoon, ownedCompany, E. D. Sassoon & Co.]
-
A.
publicCompany
Indicates that a company is publicly traded, meaning its ownership shares are available to the general public on one or more stock exchanges.
-
B.
memberCompany
Indicates that a company is formally part of, or affiliated as a member with, a larger organization, group, or association.
-
C.
residentCompany
Indicates that a company is based in, operates from, or has its primary residence in a particular location or jurisdiction.
-
D.
homeCompany
Indicates that one entity serves as the primary or base company associated with another entity, such as a person or subsidiary.
-
E.
isPrivateCompany
Indicates that an entity operates as a privately held company, not publicly traded on a stock exchange.
- F. None of above. chosen
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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed4297c81909062f19b7795f181 |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:19 p.m.