Triple
T28970703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNITE HERE |
E734262
|
entity |
| Predicate | representsWorkersInIndustry |
P193054
|
FINISHED |
| Object | hotel 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: hotel industry | Statement: [UNITE HERE, representsWorkersInIndustry, hotel industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsWorkersInIndustry Context triple: [UNITE HERE, representsWorkersInIndustry, hotel industry]
-
A.
representsWorkersOf
Indicates a relationship where one entity denotes or stands for the workers associated with another entity.
-
B.
involvesWorkers
Indicates that an event, process, or situation includes workers as active participants or affected parties.
-
C.
occupantIndustry
Indicates the industry or sector in which an occupant (such as a tenant or user of a space) operates.
-
D.
representedOccupation
Indicates that one entity has served as an official or formal representative of another entity’s occupation or professional role.
-
E.
organizedWorkersIn
Indicates that an entity took action to organize or unionize workers within a particular group, workplace, or organization.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: April 28, 2026, 9:05 a.m.