Triple
T38570119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satriale’s Pork Store |
E929240
|
entity |
| Predicate | associatedMediumCompany |
P40171
|
FINISHED |
| Object | HBO |
E18702
|
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: HBO | Statement: [Satriale’s Pork Store, associatedMediumCompany, HBO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMediumCompany Context triple: [Satriale’s Pork Store, associatedMediumCompany, HBO]
-
A.
hasMediaCompany
chosen
Indicates that one entity owns, controls, or is formally associated with a media company.
-
B.
memberCompany
Indicates that a company is formally part of, or affiliated as a member with, a larger organization, group, or association.
-
C.
associatedCompanyGlobalScope
Indicates that there is a relationship linking an entity to a company at a global (worldwide) organizational scope.
-
D.
associatedCompanyKnownFor
Indicates that a company linked to an entity is recognized or notable for a particular product, service, activity, or characteristic.
-
E.
associatedWithCompanyMarket
Indicates a relationship where a company is linked or connected to a specific market in which it operates, targets, or has a presence.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41e04552ac81909d54f56dc69cf5a4 |
completed | June 29, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.