Triple
T34038941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Osuna |
E872882
|
entity |
| Predicate | hasNobleTitleStyle |
P76052
|
FINISHED |
| Object | Excelentísimo Señor |
E415810
|
NE 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: Excelentísimo Señor | Statement: [Duke of Osuna, hasNobleTitleStyle, Excelentísimo Señor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobleTitleStyle Context triple: [Duke of Osuna, hasNobleTitleStyle, Excelentísimo Señor]
-
A.
nobleTitleStyle
chosen
Indicates the specific form or style in which a person's noble title is expressed or formally rendered.
-
B.
hasNobleTitleCount
Indicates the number of noble titles that are associated with or held by a given entity.
-
C.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
D.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
E.
hasHeraldicTitle
Indicates that an entity holds or is associated with a specific heraldic title or rank within a heraldic system.
- F. None of above.
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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a02efcb13248190a0bef09ba7869ada |
completed | May 12, 2026, 9:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36a038eab48190b2912432d0aff8cc |
completed | June 20, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_6a024995e1d081908783ca294d1397c3 |
completed | May 11, 2026, 9:26 p.m. |
Created at: May 1, 2026, 1:51 a.m.