Triple
T23978692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agnes van Rhijn |
E604444
|
entity |
| Predicate | attitudeTowardChange |
P151815
|
FINISHED |
| Object | resistant |
—
|
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: resistant | Statement: [Agnes van Rhijn, attitudeTowardChange, resistant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attitudeTowardChange Context triple: [Agnes van Rhijn, attitudeTowardChange, resistant]
-
A.
attitudeTowardReform
chosen
Indicates an entity’s stance, opinion, or disposition regarding a proposed or ongoing reform.
-
B.
changesMindAfter
Indicates that one entity revises or reverses a previously held decision, opinion, or intention after another entity’s action, statement, or influence.
-
C.
cultAttitude
Indicates the stance, beliefs, or disposition that a cult or cult-like group holds toward a particular entity, idea, or practice.
-
D.
conceptualizesChangeAs
Indicates that one entity understands, frames, or interprets a change in terms of another concept or model.
-
E.
attitudeTowardSocialNorms
Indicates an entity’s stance, feelings, or orientation regarding prevailing social rules, expectations, or norms.
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2bc79688190bc98a2d57b91f5a3 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:26 p.m.