Triple
T5680791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LORT theater |
E125192
|
entity |
| Predicate | laborRelationsFramework |
P3027
|
FINISHED |
| Object | unionized |
—
|
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: unionized | Statement: [LORT theater, laborRelationsFramework, unionized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laborRelationsFramework Context triple: [LORT theater, laborRelationsFramework, unionized]
-
A.
laborRelationsIssue
Indicates a relationship where there is a dispute, concern, or matter involving labor relations between workers (or their representatives) and employers.
-
B.
mainLaborLaw
Indicates that the referenced law is the primary or governing labor/employment law applicable to the situation or entities involved.
-
C.
laborSystem
chosen
Indicates the type or structure of work organization, employment arrangements, and labor relations that govern how work is performed and managed.
-
D.
laborUnion
Indicates that an entity is a labor union representing workers in collective employment-related matters.
-
E.
laborProvision
Indicates the provision or supply of labor or workforce from one party to another for work or services.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.