Triple
T11484601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davis-Bacon and Related Acts |
E272242
|
entity |
| Predicate | appliesToWorkers |
P3807
|
FINISHED |
| Object | laborers |
—
|
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: laborers | Statement: [Davis-Bacon and Related Acts, appliesToWorkers, laborers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToWorkers Context triple: [Davis-Bacon and Related Acts, appliesToWorkers, laborers]
-
A.
appliesToWork
Indicates that something (such as a rule, policy, condition, or attribute) is relevant to, governs, or is in effect for a particular piece of work or work-related activity.
-
B.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
C.
involvesWorkers
chosen
Indicates that an event, process, or situation includes workers as active participants or affected parties.
-
D.
respondsToWork
Indicates that one entity replies or reacts to another entity’s work, output, or contribution.
-
E.
appliesToPerson
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific person.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a1ea00c8190b42cdc13a6bc61c3 |
completed | April 10, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.