Triple
T26568462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Battle of Kosovo |
E666755
|
entity |
| Predicate | hasSultanOfOttomans |
P30324
|
FINISHED |
| Object | Murad II |
—
|
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: Murad II | Statement: [Second Battle of Kosovo, hasSultanOfOttomans, Murad II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSultanOfOttomans Context triple: [Second Battle of Kosovo, hasSultanOfOttomans, Murad II]
-
A.
OttomanDynasty
Indicates a dynastic or ruling-family relationship associated with the Ottoman Empire.
-
B.
OttomanRole
chosen
Indicates that an entity holds or held a specific role, position, or function within the Ottoman Empire.
-
C.
OttomanName
Indicates that an entity has a name or designation used during the Ottoman Empire period.
-
D.
underOttomanRuleFrom
Indicates that one entity was under the political authority or control of the Ottoman Empire starting from a specified time.
-
E.
wasOttomanCity
Indicates that a location previously functioned as a city within the territorial or administrative domain of the Ottoman Empire.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 1:56 a.m.