Triple
T25735180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montagnana |
E645356
|
entity |
| Predicate | fortificationsPeriod |
P77894
|
FINISHED |
| Object | 13th–14th 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–14th century | Statement: [Montagnana, fortificationsPeriod, 13th–14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortificationsPeriod Context triple: [Montagnana, fortificationsPeriod, 13th–14th century]
-
A.
eraOfFortification
chosen
Indicates the historical time period during which a structure or site was fortified or equipped with defensive works.
-
B.
eraOfMajorFortification
Indicates the historical period during which a structure or site underwent its primary or most significant phase of fortification.
-
C.
fortificationsLaterControlledBy
Indicates that control over certain fortifications passed to a different entity at a later time.
-
D.
hasCityWallsFromPeriod
Indicates that a city possesses defensive walls that date from a specified historical period.
-
E.
earliestRecordedFortification
Indicates that the subject is the earliest known or first historically recorded example of a particular fortification associated with the object.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fcbead288190ad04ffa3c4d463be |
completed | May 2, 2026, 1:31 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 11:24 p.m.