Triple
T27278469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inchaffray Abbey |
E688262
|
entity |
| Predicate | elevatedToAbbeyDate |
P50845
|
FINISHED |
| Object | early 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: early 13th century | Statement: [Inchaffray Abbey, elevatedToAbbeyDate, early 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToAbbeyDate Context triple: [Inchaffray Abbey, elevatedToAbbeyDate, early 13th century]
-
A.
elevationToAbbeyDate
chosen
Indicates the date on which an entity was formally elevated to the status of an abbey.
-
B.
elevatedToImperialAbbey
Indicates that a religious abbey was granted the status of an Imperial Abbey, becoming directly subject to the authority of the emperor rather than to local or regional lords.
-
C.
elevatedToRoyalAbbey
Indicates that a religious institution was formally granted the status and privileges of a royal abbey by a monarch or ruling authority.
-
D.
elevationToKingshipDate
Indicates the date on which an entity was formally elevated or raised to the status of kingship.
-
E.
elevatedToArchbishopDate
Indicates the date on which an individual was formally elevated to the rank or office of archbishop.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 11:05 a.m.