Triple
T23414987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess of Villafranca del Bierzo |
E560179
|
entity |
| Predicate | grandeeship |
P71268
|
FINISHED |
| Object | Grandee of Spain |
—
|
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: Grandee of Spain | Statement: [Marquess of Villafranca del Bierzo, grandeeship, Grandee of Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandeeship Context triple: [Marquess of Villafranca del Bierzo, grandeeship, Grandee of Spain]
-
A.
holdsGrandeeship
chosen
Indicates that one entity possesses or occupies the status, office, or title of a grandee in relation to another entity or domain.
-
B.
numberOfGrandeeships
Indicates the quantity of grandeeships (noble titles or ranks of grandee status) associated with a given entity.
-
C.
noblePrivilege
Indicates that an entity possesses special rights, immunities, or advantages granted by virtue of noble or aristocratic status.
-
D.
aristocraticTitleHeldFrom
Indicates the time period or starting point from which an aristocratic title was held by an entity.
-
E.
nobleTitleElevated
Indicates that an entity’s noble rank or title has been raised to a higher level of nobility.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a514b1d08190bbde2c3714c996fd |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:39 p.m.