Triple
T31739347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitulations of Santa Fe |
E810090
|
entity |
| Predicate | grantedNobilityStatus |
P154954
|
FINISHED |
| Object | Columbus family |
—
|
NE NERFINISHED |
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: Columbus family | Statement: [Capitulations of Santa Fe, grantedNobilityStatus, Columbus family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedNobilityStatus Context triple: [Capitulations of Santa Fe, grantedNobilityStatus, Columbus family]
-
A.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
B.
nobleTitleGranted
chosen
Indicates that a noble title has been formally conferred upon an entity by an authorized grantor or authority.
-
C.
nobleRankGrantedBy
Indicates that a particular noble rank or title was formally conferred upon someone by a specific granting authority or person.
-
D.
nobleTitleAcquiredThrough
Indicates the manner, event, or process by which a person comes to obtain or be granted a particular noble title.
-
E.
noblePrivilege
Indicates that an entity possesses special rights, immunities, or advantages granted by virtue of noble or aristocratic status.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 30, 2026, 11:24 p.m.