Triple
T10385289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visconti family |
E244743
|
entity |
| Predicate | dynastyEnded |
P59019
|
FINISHED |
| Object | 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: 15th century | Statement: [Visconti family, dynastyEnded, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyEnded Context triple: [Visconti family, dynastyEnded, 15th century]
-
A.
dynastyEndedWith
chosen
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
B.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
C.
dynastyConfirmed
Indicates that a particular ruling dynasty has been officially verified or recognized as legitimate in a given context.
-
D.
hasLastDynasty
Indicates that an entity’s most recent or final ruling dynasty is the specified dynasty.
-
E.
dynastyRestored
Indicates that a previously displaced ruling dynasty has been returned to power or reestablished as the legitimate authority.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9a42e748190b10fa7b4ca006bad |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:04 p.m.