Triple
T26808003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doge of Venice |
E671897
|
entity |
| Predicate | officeHolderRestrictions |
P2718
|
FINISHED |
| Object | had to be male |
—
|
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: had to be male | Statement: [Doge of Venice, officeHolderRestrictions, had to be male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHolderRestrictions Context triple: [Doge of Venice, officeHolderRestrictions, had to be male]
-
A.
officeHoldersMustNot
Indicates that certain individuals are prohibited from holding specified offices or positions.
-
B.
officeHoldersMustBe
chosen
Indicates that individuals who hold a particular office are required to possess a specified status, qualification, or characteristic.
-
C.
officeHoldersMustComplyWith
Indicates that individuals holding an office are obligated to follow or adhere to the specified rules, directives, or requirements.
-
D.
officeHoldersNumberLimit
Indicates a constraint specifying the maximum number of individuals who may simultaneously hold a particular office or position.
-
E.
officeHolderNotRequired
Indicates that holding a particular office or position is not mandatory for the related role, action, or status to apply.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 27, 2026, 4:27 a.m.