Triple
T34397563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbasid invasion of Anatolia in 838 |
E882873
|
entity |
| Predicate | impactOnByzantium |
P182432
|
FINISHED |
| Object | weakening of Anatolian defenses |
—
|
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: weakening of Anatolian defenses | Statement: [Abbasid invasion of Anatolia in 838, impactOnByzantium, weakening of Anatolian defenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnByzantium Context triple: [Abbasid invasion of Anatolia in 838, impactOnByzantium, weakening of Anatolian defenses]
-
A.
impactOnByzantines
chosen
Indicates the effect or influence that something has on the Byzantines.
-
B.
impactOnConstantinople
Indicates a relationship where one entity has an effect, influence, or consequence specifically on the city of Constantinople.
-
C.
aimOfByzantines
Indicates the goal or objective pursued by the Byzantines in a given context.
-
D.
allyOfByzantines
Indicates a relationship where an entity served as an ally or cooperative partner of the Byzantine Empire.
-
E.
statusInByzantineEmpire
Indicates the role, rank, or condition an entity held within the political or social structure of the Byzantine 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:59 a.m.