Triple
T14277312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherborne |
E353947
|
entity |
| Predicate | oldCastleConstructionCentury |
P6333
|
FINISHED |
| Object | 12th 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: 12th century | Statement: [Sherborne, oldCastleConstructionCentury, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oldCastleConstructionCentury Context triple: [Sherborne, oldCastleConstructionCentury, 12th century]
-
A.
castleBuilt
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
B.
constructionCentury
chosen
Indicates the century during which something was constructed or built.
-
C.
fortressWallBuiltInCentury
Indicates that a fortress wall was constructed during a specified century.
-
D.
originalCastleFoundedIn
Indicates the specific year or time period when the original version of a castle was first established or built.
-
E.
containsBuildingFromCentury
Indicates that a location or area includes at least one building that originates from a specified century.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6583f0ec81909ebfc7a2c6351ff8 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.