Triple
T13520608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Gorizia |
E322882
|
entity |
| Predicate | extinctDynasty |
P110086
|
FINISHED |
| Object | 1500 |
—
|
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: 1500 | Statement: [County of Gorizia, extinctDynasty, 1500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extinctDynasty Context triple: [County of Gorizia, extinctDynasty, 1500]
-
A.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
B.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
-
C.
founderDynasty
Indicates that an entity is the founding member or originator of a particular dynasty.
-
D.
hasLastDynasty
Indicates that an entity’s most recent or final ruling dynasty is the specified dynasty.
-
E.
dominantDynasty
Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
- F. None of above. chosen
Provenance (4 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa3df0c8190804174695587f0ea |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaee128d88190b097be17fdd2f92b |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:44 p.m.