Triple
T20835758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vijećnica |
E512954
|
entity |
| Predicate | majorReconstructionPhase |
P54016
|
FINISHED |
| Object | 1996–2014 |
—
|
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: 1996–2014 | Statement: [Vijećnica, majorReconstructionPhase, 1996–2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorReconstructionPhase Context triple: [Vijećnica, majorReconstructionPhase, 1996–2014]
-
A.
hasMajorReconstruction
Indicates that an entity has undergone a significant or extensive reconstruction or renovation.
-
B.
majorRedevelopmentPeriod
chosen
Indicates a time span during which a place or structure underwent significant redevelopment or large-scale renovation.
-
C.
majorPhase
Indicates that one phase is a primary or dominant stage within a larger process, lifecycle, or sequence.
-
D.
majorRebuilder
Indicates that an entity plays a primary or leading role in reconstructing, restoring, or significantly rebuilding another entity.
-
E.
majorConstruction
Indicates a relationship where a construction project is large-scale, significant, or of primary importance in scope, impact, or resources.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c326daec8190bd4caa41a4b38833 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:42 p.m.