Triple
T7012277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunnottar Castle |
E162610
|
entity |
| Predicate | earlierFortificationFromCentury |
P28167
|
FINISHED |
| Object | 7th 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: 7th century | Statement: [Dunnottar Castle, earlierFortificationFromCentury, 7th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierFortificationFromCentury Context triple: [Dunnottar Castle, earlierFortificationFromCentury, 7th century]
-
A.
fortressWallBuiltInCentury
Indicates that a fortress wall was constructed during a specified century.
-
B.
earliestRecordedFortification
chosen
Indicates that the subject is the earliest known or first historically recorded example of a particular fortification associated with the object.
-
C.
attestedUntilCentury
Indicates the latest century up to which the existence or use of something is historically documented or evidenced.
-
D.
constructionCentury
Indicates the century during which something was constructed or built.
-
E.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc58b04c8190af4913dbaf43c3d4 |
completed | March 27, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c790288190b7cbbaa4a5f9c91d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:34 p.m.