Triple
T25059281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess Palatine of the Rhine |
E627610
|
entity |
| Predicate | superordinateTitle |
P54213
|
FINISHED |
| Object | Electress Palatine |
—
|
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: Electress Palatine | Statement: [Countess Palatine of the Rhine, superordinateTitle, Electress Palatine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superordinateTitle Context triple: [Countess Palatine of the Rhine, superordinateTitle, Electress Palatine]
-
A.
higherTitleOf
Indicates that one entity holds a job or position title that is hierarchically superior to the title held by another entity.
-
B.
centralTitle
Indicates that one title functions as the primary or main title in relation to other associated titles.
-
C.
standardTitle
Indicates that an entity has a primary or official title or name by which it is commonly recognized.
-
D.
parentTitle
chosen
Indicates that one entity has a title that is the parent or higher-level title of another entity’s title in a hierarchical structure.
-
E.
aggregateTitle
Indicates that one entity serves as a collective or overarching title that groups or summarizes multiple related items or works.
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 18, 2026, 6:09 a.m.