Triple
T33540427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Signore di Milano |
E859054
|
entity |
| Predicate | hasTypeOfRulership |
P198835
|
FINISHED |
| Object | signoria |
—
|
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: signoria | Statement: [Signore di Milano, hasTypeOfRulership, signoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfRulership Context triple: [Signore di Milano, hasTypeOfRulership, signoria]
-
A.
hasTypeOfRuler
Indicates that one entity serves as the specific kind or category of ruler (e.g., monarch, dictator, president) that characterizes or governs another entity.
-
B.
hasRulingPeople
Indicates that a group or entity serves as the governing or ruling authority over another entity.
-
C.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
D.
hasRulingCrown
Indicates that one entity possesses or wears a crown that signifies authority or rulership over a domain or group.
-
E.
typeOfOverlordship
Indicates a hierarchical relationship in which one entity holds overlordship, or superior controlling authority, over another.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69ff0d800ee88190835e233d9e846cdb |
completed | May 9, 2026, 10:33 a.m. |
Created at: May 1, 2026, 1:39 a.m.