Triple
T6207865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunvegan Castle |
E138792
|
entity |
| Predicate | builtFromCentury |
P6333
|
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: [Dunvegan Castle, builtFromCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtFromCentury Context triple: [Dunvegan Castle, builtFromCentury, 13th century]
-
A.
constructionCentury
chosen
Indicates the century during which something was constructed or built.
-
B.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other entity.
-
C.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
-
D.
rebuiltInCentury
Indicates that an existing structure or entity was reconstructed or significantly rebuilt during a specified century.
-
E.
developedSinceCentury
Indicates that something began to be developed or came into existence starting from a specified century onward.
- 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062870d5881909b8d4e33ff31a907 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.