Triple
T12925326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Nuit étoilée sur le Rhône |
E309228
|
entity |
| Predicate | subject heading |
P33059
|
FINISHED |
| Object | night in art |
—
|
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: night in art | Statement: [La Nuit étoilée sur le Rhône, subject heading, night in art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subject heading Context triple: [La Nuit étoilée sur le Rhône, subject heading, night in art]
-
A.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
B.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
C.
subtitle
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
-
D.
libraryOfCongressSubjectHeading
chosen
Indicates that one entity is a Library of Congress Subject Heading used as the controlled subject term for describing or indexing the other entity.
-
E.
subjectOfWork
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971eb17c88190bf523da897172a0c |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fab4d0881909a7a4d66bab9aa85 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.