Triple
T1150115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reorganization Plan No. 1 of 1953 |
E23656
|
entity |
| Predicate | affectedFunction |
P26088
|
FINISHED |
| Object | federal health programs |
—
|
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: federal health programs | Statement: [Reorganization Plan No. 1 of 1953, affectedFunction, federal health programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedFunction Context triple: [Reorganization Plan No. 1 of 1953, affectedFunction, federal health programs]
-
A.
associatedFunction
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
B.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
C.
possibleFunction
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
-
D.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
E.
intendedFunction
Indicates that something is designed or purposed to perform a particular role, use, or function.
- F. None of above. chosen
Provenance (4 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bd0ab5f88190bb583fc63b4cc150 |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:44 p.m.