Triple
T27119002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Commercy |
E686935
|
entity |
| Predicate | hasRankInNobilityHierarchy |
P80950
|
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: [Prince of Commercy, hasRankInNobilityHierarchy, high nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankInNobilityHierarchy Context triple: [Prince of Commercy, hasRankInNobilityHierarchy, high nobility]
-
A.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
B.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
C.
nobleRankInHierarchy
chosen
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
-
D.
parentalNobilityRank
Indicates the comparative social or noble status level held by a subject’s parent(s) within a hierarchy of nobility.
-
E.
positionOnNobility
Indicates the rank or status an entity holds 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 8:58 a.m.