Triple
T14164636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gay Perry |
E351039
|
entity |
| Predicate | worksAsConsultantFor |
P113078
|
FINISHED |
| Object | Hollywood film productions |
—
|
LITERAL 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: Hollywood film productions | Statement: [Gay Perry, worksAsConsultantFor, Hollywood film productions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksAsConsultantFor Context triple: [Gay Perry, worksAsConsultantFor, Hollywood film productions]
-
A.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
B.
developerOfWork
Indicates that one entity is the creator or producer responsible for making or developing a particular work.
-
C.
workAt
Indicates that an entity is employed by or performs work for a particular organization, company, or place.
-
D.
worksInOrganizationType
Indicates that an entity is employed by or performs work within an organization of a specified type (e.g., company, nonprofit, government agency).
-
E.
hasWorksIn
Indicates that one entity is employed by or performs their professional activities within the organization, location, or context represented by another entity.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b207cc8190b85b1ff0910b54da |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:59 a.m.