Triple
T16734083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruce Castle |
E406671
|
entity |
| Predicate | centuryOfSignificantRebuilding |
P11509
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Bruce Castle, centuryOfSignificantRebuilding, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centuryOfSignificantRebuilding Context triple: [Bruce Castle, centuryOfSignificantRebuilding, 17th century]
-
A.
rebuiltInCentury
chosen
Indicates that an existing structure or entity was reconstructed or significantly rebuilt during a specified century.
-
B.
partiallyRebuiltInCentury
Indicates that an entity underwent partial reconstruction or significant repair during the specified century.
-
C.
eraOfMajorConstruction
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
D.
constructionCentury
Indicates the century during which something was constructed or built.
-
E.
reorganizedInCentury
Indicates that an entity underwent a significant reorganization or structural change during the 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c38c9cc8190a3220cc3684388dc |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.