Triple
T22996739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | After Goya |
E572216
|
entity |
| Predicate | titleUsesPhrase |
P22461
|
FINISHED |
| Object | After [artist] convention in art titling |
—
|
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: After [artist] convention in art titling | Statement: [After Goya, titleUsesPhrase, After [artist] convention in art titling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleUsesPhrase Context triple: [After Goya, titleUsesPhrase, After [artist] convention in art titling]
-
A.
titlePhrase
chosen
Indicates that one entity is a phrase functioning as the title or name of another entity.
-
B.
usesTitleIn
Indicates that an entity is referred to using a particular title within a specified context or medium.
-
C.
titleUsage
Indicates how a title is applied, referenced, or used in relation to an entity or context.
-
D.
titlePattern
Indicates that there is a specific structural or textual pattern that the title of an entity is expected to follow.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f3186c81909e0d5177029a72ae |
completed | April 29, 2026, 4:02 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.