Triple
T11560009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriarch of Venice |
E274115
|
entity |
| Predicate | patriarchalTitleType |
P100320
|
FINISHED |
| Object | titular patriarchate |
—
|
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: titular patriarchate | Statement: [Patriarch of Venice, patriarchalTitleType, titular patriarchate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patriarchalTitleType Context triple: [Patriarch of Venice, patriarchalTitleType, titular patriarchate]
-
A.
patriarchTitle
Indicates that one entity holds the role or title of patriarch in relation to another entity.
-
B.
patriarchalTitleUsage
Indicates that a title or form of address is used in a way that reflects or reinforces a male-dominated, patriarchal social or familial hierarchy.
-
C.
patriarchalName
Indicates that one entity bears a name derived from or assigned according to a patriarchal (male-line or father-based) naming convention in relation to another entity.
-
D.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
E.
fatherTitle
Indicates the formal title or designation held by a person's father.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a899d4481909a3bce3147763b51 |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:37 p.m.