Triple
T9559834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthony Blunt |
E230639
|
entity |
| Predicate | academicWork |
P53896
|
FINISHED |
| Object | studies of Nicolas Poussin |
—
|
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: studies of Nicolas Poussin | Statement: [Anthony Blunt, academicWork, studies of Nicolas Poussin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academicWork Context triple: [Anthony Blunt, academicWork, studies of Nicolas Poussin]
-
A.
scholarlyWork
chosen
Indicates a relationship where an entity is a formal academic or research work produced, published, or recognized within a scholarly context.
-
B.
academicBody
Indicates a formal organizational relationship in which an entity functions as an academic institution or governing academic unit associated with another entity.
-
C.
mediumOfAcademicWork
Indicates that a particular medium or format is the channel through which an academic work is expressed, recorded, or communicated.
-
D.
academicUse
Indicates that something is intended for, suitable for, or used within an academic or educational context.
-
E.
academicFocus
Indicates the primary field of study, discipline, or subject area that an entity concentrates on academically.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd994bde0c8190afcba5cb8fa8b984 |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.