Triple
T414351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wage and Hour Division |
E9558
|
entity |
| Predicate | typeOfLawEnforced |
P6527
|
FINISHED |
| Object | wage and hour law |
—
|
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: wage and hour law | Statement: [Wage and Hour Division, typeOfLawEnforced, wage and hour law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLawEnforced Context triple: [Wage and Hour Division, typeOfLawEnforced, wage and hour law]
-
A.
enforcedLaw
Indicates that an authority actively applies or upholds a specific law to regulate behavior or resolve situations.
-
B.
typeOfLawEnforcement
Indicates that one entity is a specific kind or category of law enforcement associated with another entity.
-
C.
typeOfLaw
chosen
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
D.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
E.
statuteInvolved
Indicates that a particular statute or legal provision is implicated, referenced, or applied in relation to a given case, event, or legal matter.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edcff4688190809d83d112ff25a5 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.