Triple
T26687976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danish Constitution of 1866 |
E672798
|
entity |
| Predicate | benefitedSocialGroup |
P108329
|
FINISHED |
| Object | large landowners |
—
|
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: large landowners | Statement: [Danish Constitution of 1866, benefitedSocialGroup, large landowners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitedSocialGroup Context triple: [Danish Constitution of 1866, benefitedSocialGroup, large landowners]
-
A.
socialGroupBenefited
chosen
Indicates that a particular social group gains an advantage, improvement, or positive impact as a result of an action, event, or resource.
-
B.
sectorBenefited
Indicates that a particular sector gains advantage, support, or positive impact from a given action, policy, resource, or entity.
-
C.
ethnicGroupHelped
Indicates that one ethnic group provided assistance or support to another entity or group.
-
D.
beneficialMembers
Indicates that certain members of a group have a positive or advantageous effect on the group or on other entities.
-
E.
vulnerableGroup
Indicates that the referenced group is at increased risk of harm, disadvantage, or negative outcomes compared to others.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 3:24 a.m.