Triple
T13181247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigevano |
E313729
|
entity |
| Predicate | PiazzaDucaleConstructionStart |
P77727
|
FINISHED |
| Object | late 15th 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: late 15th century | Statement: [Vigevano, PiazzaDucaleConstructionStart, late 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PiazzaDucaleConstructionStart Context triple: [Vigevano, PiazzaDucaleConstructionStart, late 15th century]
-
A.
cathedralConstructionStarted
Indicates that the process of constructing a cathedral has begun.
-
B.
royalPalaceConstructionPeriod
Indicates the time span during which a royal palace was built or under construction.
-
C.
ducalReignStart
Indicates the point in time when an individual begins their tenure or rule as a duke.
-
D.
monumentConstructionStart
chosen
Indicates the date or time when the construction of a monument was begun.
-
E.
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.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.