Triple
T3530766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Mecklenburg |
E74652
|
entity |
| Predicate | aristocraticClass |
P9679
|
FINISHED |
| Object | Mecklenburg 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: Mecklenburg nobility | Statement: [Duchy of Mecklenburg, aristocraticClass, Mecklenburg nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aristocraticClass Context triple: [Duchy of Mecklenburg, aristocraticClass, Mecklenburg nobility]
-
A.
nobilityClass
chosen
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
B.
aristocraticRole
Indicates that an entity holds or is associated with a formal position, title, or function within an aristocratic or noble hierarchy.
-
C.
traditionalSocialClass
Indicates that an entity belongs to or is associated with a particular traditional social class within a social hierarchy.
-
D.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
-
E.
dominantSocialClass
Indicates that one social class holds primary power, influence, or status over others within a given social structure or context.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc988ee081909c6b9d5eed0d2d6d |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.