Triple
T34884518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelloe, Durham, England |
E1006105
|
entity |
| Predicate | hasAssociatedArtwork |
P63916
|
FINISHED |
| Object | Kelloe Cross |
—
|
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: Kelloe Cross | Statement: [Kelloe, Durham, England, hasAssociatedArtwork, Kelloe Cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedArtwork Context triple: [Kelloe, Durham, England, hasAssociatedArtwork, Kelloe Cross]
-
A.
hasArtworksFrom
Indicates that one entity possesses or includes artworks that originate from or are created by another entity.
-
B.
hasPublicArtwork
Indicates that a location or entity possesses or features artwork that is accessible to the general public.
-
C.
associatedWithWorkOfArt
chosen
Indicates a relationship in which an entity is connected or related to a specific work of art, such as through creation, contribution, ownership, or contextual association.
-
D.
hasArtisticWorks
Indicates that an entity possesses, is associated with, or is the creator of one or more artistic works.
-
E.
hasArtCollection
Indicates that an entity possesses, maintains, or is associated with a collection of artworks.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4 p.m.