Triple
T14845020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAG-AFTRA members |
E349063
|
entity |
| Predicate | workInIndustry |
P51954
|
FINISHED |
| Object | film industry |
—
|
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: film industry | Statement: [SAG-AFTRA members, workInIndustry, film industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInIndustry Context triple: [SAG-AFTRA members, workInIndustry, film industry]
-
A.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
B.
workRelatedTo
Indicates a relationship where one entity’s work, tasks, or professional activities are connected, associated, or relevant to those of another entity.
-
C.
positionInIndustry
Indicates the role, rank, or standing that an entity holds within a particular industry or sector.
-
D.
appliedWork
Indicates that an entity has put effort, skill, or labor into performing or producing a particular work or task.
-
E.
industryConnection
chosen
Indicates a professional or business relationship linking entities within the same or related industries, such as partnerships, collaborations, or shared sector involvement.
- F. None of above.
Provenance (3 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded291103c8190a64cfe700bfee197 |
completed | April 14, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:53 a.m.