Triple
T2390806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolwyddelan Castle |
E48936
|
entity |
| Predicate | garrisonedUntil |
P26563
|
FINISHED |
| Object | 14th 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: 14th century | Statement: [Dolwyddelan Castle, garrisonedUntil, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonedUntil Context triple: [Dolwyddelan Castle, garrisonedUntil, 14th century]
-
A.
garrisonUseUntil
chosen
Indicates that a garrison occupies or utilizes a location or resource up to a specified end time or condition.
-
B.
laterGarrisonedBy
Indicates that a location or structure was subsequently occupied and used as a military garrison by a specified force or group.
-
C.
garrisonDuringWar
Indicates that a military force is stationed in a specific location for defense or control during a time of war.
-
D.
garrisonedForce
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
-
E.
garrisonAfterWar
Indicates that a military force is stationed in or occupies a location following the end of a war or major conflict.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc87457388190822d5506327db8f2 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.