Triple
T27324762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catherine of Courtenay |
E689609
|
entity |
| Predicate | paternalTitleInherited |
P162186
|
FINISHED |
| Object | claims to the Latin Empire |
—
|
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: claims to the Latin Empire | Statement: [Catherine of Courtenay, paternalTitleInherited, claims to the Latin Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paternalTitleInherited Context triple: [Catherine of Courtenay, paternalTitleInherited, claims to the Latin Empire]
-
A.
paternalTitleFamily
Indicates a familial relationship where one entity holds a paternal title (such as father, grandfather, or paternal ancestor) in relation to another within a family structure.
-
B.
fatherTitleAtBirth
Indicates the formal title or honorific held by a person's father at the time of that person's birth.
-
C.
fatherTitle
Indicates the formal title or designation held by a person's father.
-
D.
patriarchTitle
Indicates that one entity holds the role or title of patriarch in relation to another entity.
-
E.
paternalTitleConnection
Indicates a relationship where one entity holds a paternal (father-related) title in connection to another entity.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f627ed03ac8190a17ddacba96f8a48 |
completed | May 2, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:35 a.m.