Triple
T2152995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FOIA Improvement Act of 2016 |
E47822
|
entity |
| Predicate | hasPresumption |
P13854
|
FINISHED |
| Object | presumption of openness |
—
|
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: presumption of openness | Statement: [FOIA Improvement Act of 2016, hasPresumption, presumption of openness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPresumption Context triple: [FOIA Improvement Act of 2016, hasPresumption, presumption of openness]
-
A.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
B.
premise
Indicates that a statement or proposition provides the foundational assumption or starting point from which a conclusion or inference is logically derived.
-
C.
has
chosen
Indicates that one entity possesses, owns, contains, or includes another entity as part of its state or composition.
-
D.
presentCondition
Indicates that an entity currently has or exhibits a particular state, situation, or condition.
-
E.
holdsFor
Indicates that a particular relationship or condition remains true over a specified interval or duration of time.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe4a3b608190b3bd5d8e28534090 |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.