Triple
T31310153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vardøhus Fortress |
E798441
|
entity |
| Predicate | currentStructurePeriod |
P74212
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Vardøhus Fortress, currentStructurePeriod, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentStructurePeriod Context triple: [Vardøhus Fortress, currentStructurePeriod, 18th century]
-
A.
currentStructure
Indicates that an entity is the present or active structural configuration or organization associated with another entity.
-
B.
eraOfCurrentStructure
Indicates the historical period or era during which the current form or configuration of the structure was established.
-
C.
mainCurrentStructuresDateFrom
Indicates the date from which the current main structures (e.g., primary configurations or versions) are considered effective or valid.
-
D.
historicalPeriodOfCurrentForm
chosen
Indicates the historical period during which the entity’s current form, structure, or configuration came into existence or was established.
-
E.
calculationPeriod
Indicates the time span or interval over which a value is computed, measured, or evaluated.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 29, 2026, 9:15 p.m.