Triple
T21217859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salon de 1846 |
E522882
|
entity |
| Predicate | eventDateReviewed |
P143244
|
FINISHED |
| Object | 1846 Paris Salon |
—
|
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: 1846 Paris Salon | Statement: [Salon de 1846, eventDateReviewed, 1846 Paris Salon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDateReviewed Context triple: [Salon de 1846, eventDateReviewed, 1846 Paris Salon]
-
A.
eventDateJudged
Indicates that a specific date has been evaluated or determined in relation to an event (e.g., as its official or relevant date).
-
B.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
C.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
D.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
E.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7347613308190a1c9f4ea51591d4b |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:42 p.m.