Triple
T34884519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelloe, Durham, England |
E1006105
|
entity |
| Predicate | hasAngloSaxonMonument |
P193083
|
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, hasAngloSaxonMonument, Kelloe Cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAngloSaxonMonument Context triple: [Kelloe, Durham, England, hasAngloSaxonMonument, Kelloe Cross]
-
A.
hasStoneMonument
Indicates that one entity possesses, contains, or features a stone monument associated with it.
-
B.
hasRomanMonument
Indicates that one entity possesses, contains, or includes a monument of Roman origin or style.
-
C.
hasMonumentInPeriod
Indicates that a monument is associated with or existed during a specified time period.
-
D.
hasPrimaryMonument
Indicates that an entity is associated with its main or most significant monument.
-
E.
hasScheduledMonument
Indicates that an entity is associated with, or contains, a site or structure officially designated as a scheduled monument.
- F. None of above. chosen
Provenance (4 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_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 3, 2026, 4 p.m.