Triple
T930205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consolidated Appropriations Act, 2023 |
E20073
|
entity |
| Predicate | includesPolicyArea |
P5037
|
FINISHED |
| Object | defense policy |
—
|
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: defense policy | Statement: [Consolidated Appropriations Act, 2023, includesPolicyArea, defense policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPolicyArea Context triple: [Consolidated Appropriations Act, 2023, includesPolicyArea, defense policy]
-
A.
coversPolicyArea
chosen
Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
-
B.
hasPolicyArea
Indicates that an entity (such as a policy, program, or initiative) is associated with or pertains to a specific policy area or domain.
-
C.
supportsPolicyArea
Indicates that one entity endorses, advocates for, or is in favor of a particular policy area or domain of public policy.
-
D.
commonPolicyArea
Indicates that two entities share the same policy domain, topic, or area of regulatory or legislative focus.
-
E.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b349b3d0819090c58b4fb60c6a1b |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b29876348190a29f4ff9878074a5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.