Triple
T32964974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Hegelians |
E843343
|
entity |
| Predicate | viewOnReform |
P16872
|
FINISHED |
| Object | preference for gradual or minimal change |
—
|
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: preference for gradual or minimal change | Statement: [Old Hegelians, viewOnReform, preference for gradual or minimal change]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnReform Context triple: [Old Hegelians, viewOnReform, preference for gradual or minimal change]
-
A.
viewsReformsAs
Indicates that one entity regards or interprets certain reforms in a particular way (e.g., as positive, negative, necessary, or harmful).
-
B.
viewOnForms
Indicates that one entity has a particular perspective, opinion, or stance regarding forms, form-related processes, or form usage.
-
C.
viewOnHereafter
Indicates a subject’s beliefs, opinions, or perspective regarding the afterlife or what happens after death.
-
D.
viewOnPolicy
Indicates a stance, opinion, or perspective that an entity holds regarding a specific policy.
-
E.
positionOnReform
chosen
Indicates a stance or viewpoint that an entity holds regarding a particular reform or set of reforms.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:21 a.m.