Triple
T24235790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peerage of Spain |
E601877
|
entity |
| Predicate | noblePrivileges |
P148343
|
FINISHED |
| Object | largely honorary in modern era |
—
|
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: largely honorary in modern era | Statement: [Peerage of Spain, noblePrivileges, largely honorary in modern era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noblePrivileges Context triple: [Peerage of Spain, noblePrivileges, largely honorary in modern era]
-
A.
noblePrivilege
chosen
Indicates that an entity possesses special rights, immunities, or advantages granted by virtue of noble or aristocratic status.
-
B.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
C.
nobilitySystem
Indicates a social or political structure in which individuals are ranked by hereditary titles or noble status.
-
D.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
E.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a9b52708190b319a9e502a61d13 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.