Triple
T37851479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Beaufort |
E944065
|
entity |
| Predicate | aristocraticRankWithinCountry |
P139814
|
FINISHED |
| Object | high-ranking French duke |
—
|
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-ranking French duke | Statement: [Duke of Beaufort, aristocraticRankWithinCountry, high-ranking French duke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aristocraticRankWithinCountry Context triple: [Duke of Beaufort, aristocraticRankWithinCountry, high-ranking French duke]
-
A.
rankRelativeToPeerage
Indicates how an entity’s hierarchical rank compares to that of a specified peer or peer group within a defined ranking system.
-
B.
aristocraticHouseStatus
Indicates the formal social or legal standing of an aristocratic house within a hierarchical nobility system.
-
C.
positionOnNobility
chosen
Indicates the rank or status an entity holds within a hierarchy of nobility.
-
D.
nobleRankOf
Indicates that one entity holds a specific noble title or rank within a hierarchical nobility system.
-
E.
parentalNobilityRank
Indicates the comparative social or noble status level held by a subject’s parent(s) within a hierarchy 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.