Triple
T37691518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bothwell lordship |
E938516
|
entity |
| Predicate | associatedWithNoblePower |
P174981
|
FINISHED |
| Object | major magnate estate |
—
|
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: major magnate estate | Statement: [Bothwell lordship, associatedWithNoblePower, major magnate estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithNoblePower Context triple: [Bothwell lordship, associatedWithNoblePower, major magnate estate]
-
A.
associatedWithNobleOrder
Indicates that an entity has a formal or recognized connection to a noble order, such as membership, affiliation, or honorary association.
-
B.
associatedNobleRank
Indicates that an entity is linked to or holds a particular noble rank or title.
-
C.
noblePowerBase
chosen
Indicates the primary social, economic, or territorial foundation from which a noble derives and exercises their power or influence.
-
D.
associatedNobleFamily
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
E.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.