Triple
T17648471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Enríquez |
E429422
|
entity |
| Predicate | memberOfNobilityRank |
P67819
|
FINISHED |
| Object | high nobility |
—
|
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: high nobility | Statement: [House of Enríquez, memberOfNobilityRank, high nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfNobilityRank Context triple: [House of Enríquez, memberOfNobilityRank, high nobility]
-
A.
associatedNobleRank
chosen
Indicates that an entity is linked to or holds a particular noble rank or title.
-
B.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
C.
nobleRankInHierarchy
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
-
D.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
E.
nobleRankGrantedBy
Indicates that a particular noble rank or title was formally conferred upon someone by a specific granting authority or person.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e3bc2f8819092e3365d9e798386 |
completed | April 19, 2026, 5:55 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:05 a.m.