Triple
T281197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impressionism |
E5357
|
entity |
| Predicate | laterReception |
P9563
|
FINISHED |
| Object | highly influential |
—
|
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: highly influential | Statement: [Impressionism, laterReception, highly influential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterReception Context triple: [Impressionism, laterReception, highly influential]
-
A.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
-
B.
party
Indicates that an entity participates as a side or participant in an event, agreement, or situation.
-
C.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
D.
announcementOccasion
Indicates the specific event, context, or circumstance on the basis of which an announcement is made.
-
E.
venue
Indicates the place or location where an event, activity, or interaction takes place.
- F. None of above. chosen
Provenance (4 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e0a23c0819083abee28b2dea49c |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b77e028819087e606fc321219f7 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25e06dd7c8190a8cbb76cee3c6e4b |
completed | Feb. 28, 2026, 3:16 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.