Triple
T35251383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Terceira |
E1018100
|
entity |
| Predicate | notableHolderPoliticalSide |
P20145
|
FINISHED |
| Object | Liberal |
—
|
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: Liberal | Statement: [Duke of Terceira, notableHolderPoliticalSide, Liberal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHolderPoliticalSide Context triple: [Duke of Terceira, notableHolderPoliticalSide, Liberal]
-
A.
notableParty
Indicates that an entity is a significant or noteworthy participant in an event, activity, or relationship.
-
B.
notableMemberParty
Indicates that a political party has a member who is particularly notable or prominent within that party.
-
C.
politicalSide
chosen
Indicates the political alignment or ideological position that one entity holds in relation to political spectra or groupings.
-
D.
notablePolitician
Indicates that the subject is a politician who is recognized as notable or significant in a political context.
-
E.
notablePartyRepresentation
Indicates that an entity is significantly or prominently represented or involved as a party in a particular event, case, or context.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.