Triple
T14845058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAG-AFTRA members |
E349063
|
entity |
| Predicate | mayJoinThrough |
P64765
|
FINISHED |
| Object | principal employment in covered 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: principal employment in covered productions | Statement: [SAG-AFTRA members, mayJoinThrough, principal employment in covered productions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayJoinThrough Context triple: [SAG-AFTRA members, mayJoinThrough, principal employment in covered productions]
-
A.
mayRejoin
Indicates that an entity is permitted or eligible to re-enter or rejoin a group, organization, or prior affiliation after having left or been removed.
-
B.
canJoin
chosen
Indicates that one entity is permitted or able to become a member or participant in another entity or group.
-
C.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
-
D.
mayActThrough
Indicates that an entity can exert influence, perform an action, or have an effect by means of another entity, mechanism, or intermediary.
-
E.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
- 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.