Triple
T37377747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helen of Brunswick-Lüneburg |
E928337
|
entity |
| Predicate | aristocracyType |
P188005
|
FINISHED |
| Object | hereditary nobility |
—
|
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 nobility | Statement: [Helen of Brunswick-Lüneburg, aristocracyType, hereditary nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aristocracyType Context triple: [Helen of Brunswick-Lüneburg, aristocracyType, hereditary nobility]
-
A.
aristocraticCenter
Indicates a central place, institution, or focal point associated with aristocratic power, influence, or activity.
-
B.
aristocraticRole
Indicates that an entity holds or is associated with a formal position, title, or function within an aristocratic or noble hierarchy.
-
C.
typeOfPolity
Indicates that one entity is a political unit and the other specifies the kind or classification of that polity (e.g., empire, kingdom, republic).
-
D.
aristocraticLegacy
Indicates that an entity inherits or is influenced by the traditions, status, or privileges associated with aristocratic lineage.
-
E.
aristocraticOrigin
Indicates that an entity originates from, or is derived from, an aristocratic or noble background.
- F. None of above. chosen
Provenance (4 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.