Triple
T1781556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnegie of Pittarrow |
E39300
|
entity |
| Predicate | nobleTitleTradition |
P11127
|
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: [Carnegie of Pittarrow, nobleTitleTradition, Scottish peerage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTitleTradition Context triple: [Carnegie of Pittarrow, nobleTitleTradition, Scottish peerage]
-
A.
traditionalCourtesyTitleHeir
Indicates that one entity holds the customary or historically recognized courtesy title associated with being the heir of another entity.
-
B.
nobleTitleNumber
Indicates the ordinal number or sequence position associated with a person's noble title (e.g., first duke, second baron).
-
C.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
D.
traditionalTitle
chosen
Indicates that an entity holds or is associated with a customary or historically established title or honorific within a cultural or social tradition.
-
E.
nobleTitleStartDate
Indicates the date on which an entity first acquired or began holding a particular noble title.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.