Triple
T7288706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tubular Bells |
E163938
|
entity |
| Predicate | hasCoverDepicting |
P15270
|
FINISHED |
| Object | bent chrome tubular bell over seascape |
—
|
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: bent chrome tubular bell over seascape | Statement: [Tubular Bells, hasCoverDepicting, bent chrome tubular bell over seascape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverDepicting Context triple: [Tubular Bells, hasCoverDepicting, bent chrome tubular bell over seascape]
-
A.
hasCoverArtFeaturing
Indicates that one entity’s cover art visually features or depicts another entity.
-
B.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
-
C.
coverArtDepicts
chosen
Indicates that the subject cover art visually represents, portrays, or includes the object within its imagery.
-
D.
isCoverOf
Indicates that one entity functions as a protective or enclosing layer placed over another entity.
-
E.
eraCovered
Indicates that one entity temporally encompasses, includes, or spans the historical period or era associated with another entity.
- 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_69c6886093b88190a254b1ce6db8bae7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb6bde448190b52852c916a8059d |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.