Triple
T33646528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uglich tragedy |
E861974
|
entity |
| Predicate | hasAssociatedNoble |
P126467
|
FINISHED |
| Object | Vasily Shuisky |
—
|
NE NERFINISHED |
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: Vasily Shuisky | Statement: [Uglich tragedy, hasAssociatedNoble, Vasily Shuisky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedNoble Context triple: [Uglich tragedy, hasAssociatedNoble, Vasily Shuisky]
-
A.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
B.
hasNobleConnection
chosen
Indicates that one entity has a familial, social, or formal association with a member of the nobility or a noble lineage.
-
C.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
D.
associatedNobleRank
Indicates that an entity is linked to or holds a particular noble rank or title.
-
E.
associatedWithNobleOrder
Indicates that an entity has a formal or recognized connection to a noble order, such as membership, affiliation, or honorary association.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:42 a.m.