Triple
T3337161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holyrood Abbey |
E70164
|
entity |
| Predicate | hasRuinedStatusSince |
P39943
|
FINISHED |
| Object | 18th century (approximate) |
—
|
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: 18th century (approximate) | Statement: [Holyrood Abbey, hasRuinedStatusSince, 18th century (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuinedStatusSince Context triple: [Holyrood Abbey, hasRuinedStatusSince, 18th century (approximate)]
-
A.
hasRuin
Indicates that one entity possesses, contains, or is associated with a ruin or ruined structure.
-
B.
hasDam
Indicates that a watercourse, reservoir, or similar feature is impounded or controlled by a specific dam.
-
C.
hadSpecialStatusIn
Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
-
D.
hasHad
chosen
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
E.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1bc31b4819085f01e0b5a7cbc5d |
completed | March 8, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.