Triple
T36085128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OnlyFans |
E1043753
|
entity |
| Predicate | hasParentCompanyJurisdiction |
P201429
|
FINISHED |
| Object | England and Wales |
—
|
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: England and Wales | Statement: [OnlyFans, hasParentCompanyJurisdiction, England and Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentCompanyJurisdiction Context triple: [OnlyFans, hasParentCompanyJurisdiction, England and Wales]
-
A.
hasParentCompanyOrigin
Indicates that an entity’s parent company originates from, or was founded in, a specified location or jurisdiction.
-
B.
hasParentOrganizationRegion
Indicates that an organization is associated with or operates under a parent organization that is based in or responsible for a specific geographic region.
-
C.
hasParentCompanyLegalForm
Indicates that an entity’s parent company possesses a specific legal form or legal organizational type.
-
D.
hasParentCompany
Indicates that one company is owned or controlled by another company that serves as its parent organization.
-
E.
hasParentCompanyHeadquarters
Indicates that a company’s parent organization has its main headquarters located at a specified place.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fff4525ce48190b1d760539e68aadc |
completed | May 10, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:08 p.m.