Triple
T34946826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lansdowne collection |
E1007876
|
entity |
| Predicate | hasArtisticPeriodCoverage |
P65827
|
FINISHED |
| Object | Renaissance |
—
|
NE NERFINISHED |
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: Renaissance | Statement: [Lansdowne collection, hasArtisticPeriodCoverage, Renaissance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisticPeriodCoverage Context triple: [Lansdowne collection, hasArtisticPeriodCoverage, Renaissance]
-
A.
timePeriodOfArt
chosen
Indicates the historical or stylistic time period during which a particular artwork or artistic activity was created or is associated.
-
B.
hasArtHistoricalSignificance
Indicates that something holds notable importance or influence within the context of art history.
-
C.
hasArtisticOrigin
Indicates that something originates from, is derived from, or is rooted in an artistic source, style, or tradition.
-
D.
hasArtisticReputation
Indicates that an entity is recognized or regarded for its artistic skill, contribution, or standing.
-
E.
hasArtHistoricalTerm
Indicates that something is associated with, labeled by, or classified using a specific term from art historical terminology.
- 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_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 3, 2026, 4 p.m.