Triple
T3039282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Báthory |
E83085
|
entity |
| Predicate | transylvanianPrincedomStart |
P1506
|
FINISHED |
| Object | 1571 |
—
|
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: 1571 | Statement: [Stephen Báthory, transylvanianPrincedomStart, 1571]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transylvanianPrincedomStart Context triple: [Stephen Báthory, transylvanianPrincedomStart, 1571]
-
A.
duchyFoundedBy
Indicates that a particular duchy was established or created by a specific person, group, or authority.
-
B.
coPrince
Indicates a relationship in which two or more individuals simultaneously share and exercise the rank and authority of prince over the same domain or polity.
-
C.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
D.
startDateAsGrandDuchy
Indicates the date on which an entity began its existence or status as a grand duchy.
-
E.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2fa52c8190a7860f762d5232ab |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.