Triple
T12671144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Visitor (Picasso at the Lapin Agile) |
E302685
|
entity |
| Predicate | appearsInTimeSetting |
P97182
|
FINISHED |
| Object | 1904 |
—
|
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: 1904 | Statement: [The Visitor (Picasso at the Lapin Agile), appearsInTimeSetting, 1904]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInTimeSetting Context triple: [The Visitor (Picasso at the Lapin Agile), appearsInTimeSetting, 1904]
-
A.
appearsInTimePeriod
chosen
Indicates that an entity is present, active, or occurs within a specified time period.
-
B.
showsTimePeriod
Indicates that one entity presents or displays a specific span or interval of time associated with another entity.
-
C.
appearsInTimePeriodDepicted
Indicates that something is present or occurs within the specific time period that is depicted or represented.
-
D.
timeOfSetting
Indicates the specific time at which an event, object, or phenomenon is set, scheduled, or takes place.
-
E.
screenTimeEra
Indicates the period or era during which a particular screen-based technology, medium, or usage pattern is prevalent or characteristic.
- 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_69d7bdee64a08190801c6d470aefd723 |
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_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.