Triple
T17944457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament of 1935–1945 |
E448667
|
entity |
| Predicate | enactedPolicyArea |
P7262
|
FINISHED |
| Object | war finance |
—
|
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: war finance | Statement: [Parliament of 1935–1945, enactedPolicyArea, war finance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enactedPolicyArea Context triple: [Parliament of 1935–1945, enactedPolicyArea, war finance]
-
A.
hasPolicyArea
chosen
Indicates that an entity (such as a policy, program, or initiative) is associated with or pertains to a specific policy area or domain.
-
B.
implementsPolicyArea
Indicates that an entity carries out, enforces, or operationalizes a specific policy area in practice.
-
C.
isPartOfPolicyArea
Indicates that one policy, topic, or issue belongs to, falls under, or is categorized within a broader policy area or domain.
-
D.
coversPolicyArea
Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
-
E.
influencedPolicyArea
Indicates that one entity has affected, shaped, or guided the development, direction, or implementation of a particular policy area associated with another entity.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9819a88190ad4ea7d562cf3f28 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.