Triple
T5428961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visby |
E121435
|
entity |
| Predicate | cityWallConstructionStart |
P14638
|
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: [Visby, cityWallConstructionStart, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityWallConstructionStart Context triple: [Visby, cityWallConstructionStart, 13th century]
-
A.
buildingConstructionStart
chosen
Indicates the point in time when the construction work on a building begins.
-
B.
cityDuringConstruction
Indicates that a city exists or is relevant during the time period in which a particular construction activity or project is taking place.
-
C.
constructionBeganAsFortressIn
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.
-
D.
startConstruction
Indicates that an entity initiates the process of building or constructing another entity or structure.
-
E.
constructionStartAfter
Indicates that the start of one construction activity or project occurs after the start of another specified construction activity or project.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.