Triple
T20744763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | post-war London |
E510549
|
entity |
| Predicate | hasKeyPolicyContext |
P141340
|
FINISHED |
| Object | Beveridge Report implementation |
—
|
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: Beveridge Report implementation | Statement: [post-war London, hasKeyPolicyContext, Beveridge Report implementation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyPolicyContext Context triple: [post-war London, hasKeyPolicyContext, Beveridge Report implementation]
-
A.
hasKeyPolicy
Indicates that an entity is associated with a specific key management or access control policy governing how its keys may be used or managed.
-
B.
hasKeyCapability
Indicates that an entity possesses an essential ability or function that is critical for performing a particular task or role.
-
C.
hasLanguagePolicyContext
Indicates that there is an associated language-related policy, rule, or regulatory context governing how language is used or managed in relation to the subject.
-
D.
hasPolicyStatus
Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
-
E.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c21197088190951a4c4a7e765891 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:33 p.m.