Triple
T8043623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Women (1907–1908) |
E187493
|
entity |
| Predicate | useOfInfluence |
P69465
|
FINISHED |
| Object | primitivism |
—
|
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: primitivism | Statement: [Three Women (1907–1908), useOfInfluence, primitivism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useOfInfluence Context triple: [Three Women (1907–1908), useOfInfluence, primitivism]
-
A.
typeOfInfluence
Indicates the specific nature or category of influence that one entity exerts on another.
-
B.
influentialFrom
chosen
Indicates that one entity has exerted influence on another, contributing to or shaping the latter’s ideas, behavior, or development.
-
C.
hasSignificantInfluenceIn
Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
-
D.
influencedDiscussionOf
Indicates that one entity had an effect on the way another entity was discussed, framed, or debated.
-
E.
influenced
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f4b5e0c819092949af0f995b850 |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:23 p.m.