Triple
T24634264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Closer |
E609760
|
entity |
| Predicate | hasCoverImageSubject |
P50487
|
FINISHED |
| Object | tomb in Staglieno Cemetery |
—
|
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: tomb in Staglieno Cemetery | Statement: [Closer, hasCoverImageSubject, tomb in Staglieno Cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverImageSubject Context triple: [Closer, hasCoverImageSubject, tomb in Staglieno Cemetery]
-
A.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
-
B.
hasCoverFeature
chosen
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
C.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
D.
hasNotableCoverOrInterpolation
Indicates that a work has a notable cover version or interpolation created by another artist.
-
E.
hasAuthorityOnCover
Indicates that one entity holds decision-making or control authority over the content, design, or use of another entity’s cover (e.g., a document, publication, or product).
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.