Triple
T12633699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotism |
E301705
|
entity |
| Predicate | hasViewOnWill |
P97623
|
FINISHED |
| Object | voluntarism |
—
|
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: voluntarism | Statement: [Scotism, hasViewOnWill, voluntarism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewOnWill Context triple: [Scotism, hasViewOnWill, voluntarism]
-
A.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
B.
hasViewOnCustom
chosen
Indicates that one entity holds or expresses a particular opinion, perspective, or stance about another entity in a customized or non-standard way.
-
C.
viewOfWill
Indicates a relationship where something represents, expresses, or reflects the will, intention, or volition of an agent.
-
D.
hasViewOnWorld
Indicates that an entity holds a particular perspective, opinion, or interpretation regarding the world or reality as a whole.
-
E.
hasViewThrough
Indicates that one entity can be seen or visually perceived through another entity acting as an intermediate medium or opening.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:15 p.m.