Triple
T34946833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lansdowne collection |
E1007876
|
entity |
| Predicate | hasKeyWorkType |
P104843
|
FINISHED |
| Object | religious painting |
—
|
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: religious painting | Statement: [Lansdowne collection, hasKeyWorkType, religious painting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyWorkType Context triple: [Lansdowne collection, hasKeyWorkType, religious painting]
-
A.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
B.
hasKeyOfWork
Indicates that one entity possesses or is associated with the key (tonal center) in which a work (such as a musical composition) is set.
-
C.
hasWorkTypeRelation
chosen
Indicates a relationship specifying the type or category of work associated with an entity.
-
D.
hasRoleInWorkType
Indicates that an entity holds a specific role or function within a particular type or category of work.
-
E.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4 p.m.