Triple
T20721321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kildalton and Oa |
E509319
|
entity |
| Predicate | knownFor |
P22
|
FINISHED |
| Object | Kildalton 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: Kildalton Cross | Statement: [Kildalton and Oa, knownFor, Kildalton Cross]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kildalton Cross Context triple: [Kildalton and Oa, knownFor, Kildalton Cross]
-
A.
Kildalton Cross
chosen
Kildalton Cross is a well-preserved 8th-century Celtic high cross on the island of Islay in Scotland, renowned for its intricate stone carvings and early Christian art.
-
B.
Crowborough Cross
Crowborough Cross is a central junction and notable local landmark in the town of Crowborough in East Sussex, England.
-
C.
Farme Cross
Farme Cross is a locality within the town of Rutherglen in South Lanarkshire, Scotland.
-
D.
Lymm Cross
Lymm Cross is a historic stone cross and local landmark situated in the village centre of Lymm, Cheshire, England.
-
E.
Stubshaw Cross
Stubshaw Cross is a residential area and local community within the town of Ashton-in-Makerfield in Greater Manchester, England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d5eec08190832ffba8a90f3076 |
completed | April 21, 2026, 12:16 a.m. |
Created at: April 16, 2026, 12:27 p.m.