Triple
T24762971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appiani family |
E619499
|
entity |
| Predicate | overlords |
P58507
|
FINISHED |
| Object | Grand Duchy of Tuscany |
—
|
NE NERFINISHED |
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: Grand Duchy of Tuscany | Statement: [Appiani family, overlords, Grand Duchy of Tuscany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overlords Context triple: [Appiani family, overlords, Grand Duchy of Tuscany]
-
A.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
B.
overlordDuringReign
Indicates that one entity served as the ruling overlord of another entity during a specified reign period.
-
C.
borderLord
Indicates that one entity serves as the feudal or territorial lord presiding over a border or frontier region associated with another entity.
-
D.
hasFeudalOverlord
chosen
Indicates that one entity holds feudal lordship or overlord authority over another, implying hierarchical control and obligations within a feudal system.
-
E.
throne
Indicates that an entity holds or occupies a position of sovereign authority or rulership, typically as a monarch.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 4:27 a.m.