Triple
T8860306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dacia Ripensis |
E210868
|
entity |
| Predicate | eventuallyLostTo |
P356
|
FINISHED |
| Object | Byzantine Empire’s Balkan enemies |
—
|
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: Byzantine Empire’s Balkan enemies | Statement: [Dacia Ripensis, eventuallyLostTo, Byzantine Empire’s Balkan enemies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventuallyLostTo Context triple: [Dacia Ripensis, eventuallyLostTo, Byzantine Empire’s Balkan enemies]
-
A.
lostTo
chosen
Indicates that one entity was defeated by another in a competition, conflict, or comparison.
-
B.
sideLost
Indicates that a particular side, party, or team was defeated or failed to win in a contest, conflict, or competition.
-
C.
canBeLostBy
Indicates that something is capable of being lost or forfeited by a particular entity.
-
D.
lostDuring
Indicates that something ceased to be in possession or was no longer retained while a particular event, process, or time period was occurring.
-
E.
surrenderedAfter
Indicates that one entity surrendered following or as a consequence of another specified event, action, or time.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e712d08190bfb1c4ba3acaea90 |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.