Triple
T21039132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunstaffnage Castle |
E518271
|
entity |
| Predicate | chapelBuiltInCentury |
P75550
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Dunstaffnage Castle, chapelBuiltInCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chapelBuiltInCentury Context triple: [Dunstaffnage Castle, chapelBuiltInCentury, 13th century]
-
A.
containsBuildingFromCentury
Indicates that a location or area includes at least one building that originates from a specified century.
-
B.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
C.
parishChurchCentury
chosen
Indicates the century during which a given parish church was established, built, or primarily dates from.
-
D.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
-
E.
completionCenturyGregorian
Indicates the century, in the Gregorian calendar system, during which the completion of something occurred.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcee13b08190a8b3372f6759cd1b |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:13 p.m.