Triple
T28859777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Estonia |
E728825
|
entity |
| Predicate | nobilityEthnicity |
P166000
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Duchy of Estonia, nobilityEthnicity, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobilityEthnicity Context triple: [Duchy of Estonia, nobilityEthnicity, German]
-
A.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
B.
nobilitySystem
Indicates a social or political structure in which individuals are ranked by hereditary titles or noble status.
-
C.
nobilityCulture
Indicates a relationship where a group’s customs, values, or practices are specifically associated with or characteristic of the nobility.
-
D.
dynasticEthnicity
Indicates the ethnic or cultural lineage associated with a particular dynasty or ruling house.
-
E.
involvedNobility
Indicates that the entities participated in or were associated with an event, action, or situation in the capacity of nobility or aristocratic status.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65bb75cd08190bbdb63c093ad6210 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 6:46 a.m.