Triple
T8706225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regatta at Molesey |
E206656
|
entity |
| Predicate | subject of |
P7040
|
FINISHED |
| Object | art historical analysis |
—
|
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: art historical analysis | Statement: [Regatta at Molesey, subject of, art historical analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subject of Context triple: [Regatta at Molesey, subject of, art historical analysis]
-
A.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
B.
subjectOfWork
chosen
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
-
C.
subjectOfProject
Indicates that an entity serves as the main focus, topic, or target of a particular project.
-
D.
mayBeSubjectOf
Indicates that an entity has the potential or possibility to serve as the subject in a given relation, event, or statement.
-
E.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58fcac748190a82b57aeb7c43df9 |
completed | March 31, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.