Triple
T29878903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ștefan Brâncoveanu |
E758820
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of Brâncoveanu family |
C56384
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: member of Brâncoveanu family Context triple: [Ștefan Brâncoveanu, instanceOf, member of Brâncoveanu family]
-
A.
member of the Vukanović dynasty
A member of the Vukanović dynasty is an individual belonging to the medieval Serbian noble family that ruled parts of the Serbian realm in the 11th and 12th centuries, descending from Vukan, a prominent branch of the Vojislavljević line.
-
B.
member of the Brus family
A member of the Brus family is an individual belonging to the Brus lineage, connected by blood, marriage, or adoption and sharing in the family’s identity, traditions, and relationships.
-
C.
member of the Dolgorukov family
A member of the Dolgorukov family is an individual belonging to the historically prominent Russian noble house of Dolgorukov, known for its political influence, military service, and close ties to the ruling dynasties.
-
D.
member of the Sobieski family
A member of the Sobieski family is an individual belonging by birth or legal relation to the historically significant Polish noble and royal lineage associated with the Sobieski name.
-
E.
member of the Godunov family
A member of the Godunov family is an individual belonging to a historically significant Russian noble lineage, often associated with political influence, landownership, and cultural heritage in Russia.
- F. None of above. chosen
Provenance (1 batch)
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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:57 p.m.