Triple
T16168217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miloslavskaya |
E392362
|
entity |
| Predicate | nobleFamilyConnected |
P13617
|
FINISHED |
| Object | Miloslavsky noble 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: Miloslavsky noble family | Statement: [Miloslavskaya, nobleFamilyConnected, Miloslavsky noble family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleFamilyConnected Context triple: [Miloslavskaya, nobleFamilyConnected, Miloslavsky noble family]
-
A.
associatedNobleFamily
chosen
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
B.
motherNobleFamily
Indicates that a person’s mother belongs to a specified noble family or house.
-
C.
associatedNobleRank
Indicates that an entity is linked to or holds a particular noble rank or title.
-
D.
usedByNobleFamily
Indicates that something is employed, possessed, or otherwise utilized by a noble family.
-
E.
notableFamilyFor
Indicates that a family is particularly recognized or distinguished for a specific person, achievement, role, or characteristic.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb4ea9c81908806f9771ae80148 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:02 a.m.