Triple
T33729771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vadstena Castle |
E864238
|
entity |
| Predicate | functionDuring16thCentury |
P180097
|
FINISHED |
| Object | defensive stronghold |
—
|
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: defensive stronghold | Statement: [Vadstena Castle, functionDuring16thCentury, defensive stronghold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuring16thCentury Context triple: [Vadstena Castle, functionDuring16thCentury, defensive stronghold]
-
A.
countryDuring16thCentury
Indicates that an entity functioned as a country or sovereign political unit during the 16th century.
-
B.
statusIn15thCentury
Indicates the status, condition, or standing that an entity had specifically during the 15th century.
-
C.
functionDuringMiddleAges
Indicates that the function, role, or activity occurred specifically during the Middle Ages period.
-
D.
inForceInLaterCenturies
Indicates that a rule, practice, or condition continued to be valid or operative during subsequent centuries after its origin.
-
E.
flourishedInCentury
Indicates that an entity experienced its peak activity, influence, or development during a specified century.
- F. None of above. chosen
Provenance (4 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: May 1, 2026, 1:44 a.m.