Triple
T36902757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Nairne |
E912083
|
entity |
| Predicate | hasNobleRankScope |
P162308
|
FINISHED |
| Object | Scottish peerage |
—
|
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: Scottish peerage | Statement: [Lord Nairne, hasNobleRankScope, Scottish peerage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobleRankScope Context triple: [Lord Nairne, hasNobleRankScope, Scottish peerage]
-
A.
nobleRankScope
chosen
Indicates the scope or domain within which a particular noble rank is valid, recognized, or applies.
-
B.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
C.
hasRoyalRankScope
Indicates that a royal rank or title is valid, applicable, or recognized only within a specified scope, such as a particular domain, territory, or context.
-
D.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
E.
hasNoblePrecedence
Indicates that one entity holds a higher rank or priority in a formal noble or aristocratic order than another entity.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.