Triple
T16742858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFSCME Local 1733 |
E406874
|
entity |
| Predicate | hasTypeOfWorker |
P104843
|
FINISHED |
| Object | garbage collectors |
—
|
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: garbage collectors | Statement: [AFSCME Local 1733, hasTypeOfWorker, garbage collectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfWorker Context triple: [AFSCME Local 1733, hasTypeOfWorker, garbage collectors]
-
A.
hasWorkforceType
Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
-
B.
hasRoleInWorkType
Indicates that an entity holds a specific role or function within a particular type or category of work.
-
C.
hasWorker
Indicates that one entity employs, utilizes, or is associated with another entity in the role of a worker.
-
D.
hasWorkTypeRelation
chosen
Indicates a relationship specifying the type or category of work associated with an entity.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa205138819080284fd9a4341225 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.