Triple
T29112633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefan Uroš V |
E736953
|
entity |
| Predicate | contemporaryEvent |
P91330
|
FINISHED |
| Object | Battle of Maritsa |
—
|
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: Battle of Maritsa | Statement: [Stefan Uroš V, contemporaryEvent, Battle of Maritsa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryEvent Context triple: [Stefan Uroš V, contemporaryEvent, Battle of Maritsa]
-
A.
contemporaryEvents
chosen
Indicates that two or more events occur in the same time period or overlap temporally.
-
B.
notableInternationalEvents
Indicates that the subject is associated with significant events that have international relevance or impact.
-
C.
politicalEvent
Indicates an occurrence related to political processes, activities, or changes involving governance, power, or public policy.
-
D.
modernCountryDuringEvent
Indicates that a modern country existed or was relevant as a political entity during the time span of a specified historical event.
-
E.
notableEventCoverage
Indicates that there is media or documented coverage specifically focused on a notable event related to the subject.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 11:19 a.m.