Triple
T627553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Carnegie, 11th Earl of Southesk |
E15851
|
entity |
| Predicate | nobilityStatus |
P1913
|
FINISHED |
| Object | hereditary peer |
—
|
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: hereditary peer | Statement: [James Carnegie, 11th Earl of Southesk, nobilityStatus, hereditary peer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobilityStatus Context triple: [James Carnegie, 11th Earl of Southesk, nobilityStatus, hereditary peer]
-
A.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
B.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
C.
hereditaryPeerage
chosen
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
D.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
E.
rankRelativeToPeerage
Indicates how an entity’s hierarchical rank compares to that of a specified peer or peer group within a defined ranking system.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e59e2688190b3c18b17c5db1e2b |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49d01b29081908be87e4cd7726ff1 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.