Triple
T15498932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maclean of Brolas |
E378896
|
entity |
| Predicate | typeOfNobleFamily |
P67660
|
FINISHED |
| Object | minor landed family |
—
|
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: minor landed family | Statement: [Maclean of Brolas, typeOfNobleFamily, minor landed family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfNobleFamily Context triple: [Maclean of Brolas, typeOfNobleFamily, minor landed family]
-
A.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
B.
nobleHouseType
chosen
Indicates the specific category or classification of a noble house (e.g., royal, ducal, baronial) within a hierarchy or system of nobility.
-
C.
headOfNobleFamily
Indicates that one entity holds the position of leader or chief authority over a particular noble family.
-
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.
motherNobleFamily
Indicates that a person’s mother belongs to a specified noble family or house.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fb0aee081909db1c54349ec8492 |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:53 a.m.