Triple
T12903805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amalgamated Clothing Workers of America |
E308679
|
entity |
| Predicate | organizedSector |
P28580
|
FINISHED |
| Object | men's clothing 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: men's clothing industry | Statement: [Amalgamated Clothing Workers of America, organizedSector, men's clothing industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedSector Context triple: [Amalgamated Clothing Workers of America, organizedSector, men's clothing industry]
-
A.
organizedAs
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
B.
organización
Indicates that an entity is an organization or participates in an organizational structure or grouping.
-
C.
sectoralOrganizations
chosen
Indicates that there is an organizational relationship specifically structured around a particular sector or industry.
-
D.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
-
E.
organizedUnder
Indicates that one entity is administratively or structurally placed within, and governed or managed by, another entity.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971820e008190bf8bc7c392c8bcbb |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.