Triple
T16279766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor of the Serbs and Greeks |
E395233
|
entity |
| Predicate | claimsOver |
P31301
|
FINISHED |
| Object | Byzantine imperial heritage |
—
|
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 imperial heritage | Statement: [Emperor of the Serbs and Greeks, claimsOver, Byzantine imperial heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsOver Context triple: [Emperor of the Serbs and Greeks, claimsOver, Byzantine imperial heritage]
-
A.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
B.
claimedRight
chosen
Indicates that an entity asserts or demands a right or entitlement in relation to another entity or resource.
-
C.
claimsToMark
Indicates that one entity asserts or alleges that it has marked, labeled, or designated another entity in some specified way.
-
D.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
-
E.
claimsEffect
Indicates that one entity asserts or states that another entity has a particular effect or impact.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24611926c81909b276ca3f406f15d |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.