Triple
T24329227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Aosta |
E613189
|
entity |
| Predicate | titleHolderCategory |
P27996
|
FINISHED |
| Object | cadet branch of the House of Savoy |
—
|
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: cadet branch of the House of Savoy | Statement: [Duke of Aosta, titleHolderCategory, cadet branch of the House of Savoy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderCategory Context triple: [Duke of Aosta, titleHolderCategory, cadet branch of the House of Savoy]
-
A.
titleHolderLabel
Indicates the entity that currently or formerly holds a specified title, position, or honor.
-
B.
titleHolderType
Indicates the specific role or capacity in which an entity holds a title (e.g., owner, trustee, beneficiary).
-
C.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
D.
titleHolderClass
chosen
Indicates the class or category of entity that holds or bears a particular title.
-
E.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ef86ec8190b27bc8cdff6c5c81 |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:55 a.m.