Triple
T1064214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Works Agency |
E22972
|
entity |
| Predicate | executiveBranchAgency |
P3933
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Federal Works Agency, executiveBranchAgency, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executiveBranchAgency Context triple: [Federal Works Agency, executiveBranchAgency, true]
-
A.
governmentBranch
Indicates that one entity functions as an official division or branch within the structure of a government.
-
B.
governmentBranchServed
Indicates that an entity has served in or been a member of a particular branch of government.
-
C.
publicAgency
chosen
Indicates that an entity functions as a government-controlled or government-authorized organization that provides public services or carries out public administration.
-
D.
createsExecutiveDepartment
Indicates that an entity establishes or brings into existence an executive-level governmental department.
-
E.
branchOfGovernmentInvolved
Indicates which branch of government (e.g., executive, legislative, judicial) is involved in or responsible for a given action, decision, or 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f85cc08190ae03ac6c84936cc5 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b7359eb881909c868a558861cc18 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.