Triple
T263617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fair Minimum Wage Act of 2007 |
E5805
|
entity |
| Predicate | legislativeTopic |
P2588
|
FINISHED |
| Object | wage regulation |
—
|
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 regulation | Statement: [Fair Minimum Wage Act of 2007, legislativeTopic, wage regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeTopic Context triple: [Fair Minimum Wage Act of 2007, legislativeTopic, wage regulation]
-
A.
relatedLegislation
Indicates that there exists a legislative document that is connected to, affects, or is otherwise relevant to the subject entity.
-
B.
legislature
Indicates that an entity serves as, or is part of, a law-making body or assembly responsible for creating or amending laws for a political unit.
-
C.
typeOfLegislation
chosen
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
D.
passedLegislation
Indicates that a governing body has formally approved and enacted a specific piece of legislation or law.
-
E.
legislativeRole
Indicates that an entity holds or performs a specific official position, function, or duty within a legislative body or lawmaking process.
- 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_69a258dd8ea08190ac554a1cc8dfd8c3 |
completed | Feb. 28, 2026, 2:54 a.m. |
| NER | Named-entity recognition | batch_69a25d8e809881908a58c9a4e3ba07c3 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.