Triple
T17665346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulevard des Capucines |
E440362
|
entity |
| Predicate | has artistic focus |
P3740
|
FINISHED |
| Object | effects of light |
—
|
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: effects of light | Statement: [Boulevard des Capucines, has artistic focus, effects of light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has artistic focus Context triple: [Boulevard des Capucines, has artistic focus, effects of light]
-
A.
hasArtisticFocus
chosen
Indicates that an entity’s primary artistic attention, theme, or specialization is directed toward a particular subject, style, or medium.
-
B.
artisticAmbition
Indicates a desire or drive to create, achieve, or excel in artistic or creative pursuits.
-
C.
artisticCenter
Indicates that a location serves as a primary hub or focal point for artistic activities, production, or cultural expression.
-
D.
artisticDirection
Indicates that one entity is responsible for guiding and overseeing the creative or aesthetic vision of another entity or project.
-
E.
artisticCharacteristic
Indicates that one entity possesses or exhibits a particular artistic quality, style, or trait in relation to another.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea8accc8190beea0900b0614020 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:56 a.m.