Triple
T22402029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varberg |
E553783
|
entity |
| Predicate | fortressConstructionBegan |
P12643
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Varberg, fortressConstructionBegan, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortressConstructionBegan Context triple: [Varberg, fortressConstructionBegan, 13th century]
-
A.
constructionBeganAsFortressIn
chosen
Indicates that the construction of something originally began with the purpose or function of serving as a fortress at a specified time or in a specified place.
-
B.
fortressBuiltAs
Indicates that a fortress was originally constructed to serve as a particular type, role, or function.
-
C.
bunkerConstructionStart
Indicates the point in time when construction work on a bunker begins.
-
D.
fortressConstructionEnd
Indicates the point in time or event when the construction of a fortress is completed.
-
E.
fortressOriginallyBuiltBy
Indicates that a particular fortress was initially constructed by a specified builder or group.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b4a96c8190838f5dda21c4d853 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.