Triple
T21279002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Robert Montgomery, 3rd Baronet of The Hall |
E524466
|
entity |
| Predicate | hasHereditaryDignity |
P52082
|
FINISHED |
| Object | baronetcy |
—
|
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: baronetcy | Statement: [Sir Robert Montgomery, 3rd Baronet of The Hall, hasHereditaryDignity, baronetcy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHereditaryDignity Context triple: [Sir Robert Montgomery, 3rd Baronet of The Hall, hasHereditaryDignity, baronetcy]
-
A.
hasHereditaryOffice
Indicates that an entity holds an office or position that is passed down through family lineage rather than acquired by election, appointment, or merit.
-
B.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
C.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
-
D.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
E.
hasNobleStatus
chosen
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
- 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73658f598819098a1192abfa40a12 |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4:02 p.m.