Triple
T22493589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Excelentísima Señora Duquesa |
E556080
|
entity |
| Predicate | requiresNobleStatus |
P121828
|
FINISHED |
| Object | duchess with grandeeship |
—
|
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: duchess with grandeeship | Statement: [Excelentísima Señora Duquesa, requiresNobleStatus, duchess with grandeeship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresNobleStatus Context triple: [Excelentísima Señora Duquesa, requiresNobleStatus, duchess with grandeeship]
-
A.
nobleRankRequired
chosen
Indicates that a certain minimum noble rank or title is required for the related action, status, or relationship to apply.
-
B.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
C.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
D.
hasNobleConnection
Indicates that one entity has a familial, social, or formal association with a member of the nobility or a noble lineage.
-
E.
requiresPremiumFor
Indicates that access to or use of something is conditional on having a premium status, subscription, or account.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb0dfb88190a4175e5e95d7ad4b |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.