Triple
T10964488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humphrey–Hawkins Act |
E259060
|
entity |
| Predicate | setsNationalGoal |
P9613
|
FINISHED |
| Object | full employment |
—
|
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: full employment | Statement: [Humphrey–Hawkins Act, setsNationalGoal, full employment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsNationalGoal Context triple: [Humphrey–Hawkins Act, setsNationalGoal, full employment]
-
A.
nationalGoals
chosen
Indicates a relationship where certain objectives or targets are officially set or recognized as the goals of a nation.
-
B.
statedAsGoalFor
Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
-
C.
politicalGoal
Indicates a relationship where an entity aims to achieve, promote, or realize a specific political outcome, policy, or state of affairs.
-
D.
legacyGoal
Indicates that an entity has a long-term, enduring objective or impact it aims to leave behind beyond its immediate actions or existence.
-
E.
strategicGoal
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77148c4588190ad0f2b54ee4bab98 |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.