Triple
T16083303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hereditary Bearer of the Crown of Scotland |
E390164
|
entity |
| Predicate | nobleRankRequired |
P121828
|
FINISHED |
| Object | peer of the realm |
—
|
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: peer of the realm | Statement: [Hereditary Bearer of the Crown of Scotland, nobleRankRequired, peer of the realm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleRankRequired Context triple: [Hereditary Bearer of the Crown of Scotland, nobleRankRequired, peer of the realm]
-
A.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
B.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
C.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
D.
nobleRankType
Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank system.
-
E.
nobleRankInHierarchy
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
- F. None of above. chosen
Provenance (4 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:59 a.m.