Triple
T22836100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cometopuli dynasty |
E565950
|
entity |
| Predicate | ledResistanceAgainst |
P55657
|
FINISHED |
| Object | Byzantine expansion in the Balkans |
—
|
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 expansion in the Balkans | Statement: [Cometopuli dynasty, ledResistanceAgainst, Byzantine expansion in the Balkans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledResistanceAgainst Context triple: [Cometopuli dynasty, ledResistanceAgainst, Byzantine expansion in the Balkans]
-
A.
resistedIn
chosen
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
-
B.
unitOfResistance
Indicates that one entity represents a unit used to measure electrical resistance of another entity.
-
C.
resistedUntil
Indicates that an entity continued to oppose or withstand another entity or force up to a specific point in time or event.
-
D.
typeOfResistance
Indicates the kind or category of resistance that characterizes how an entity opposes, impedes, or withstands another entity or influence.
-
E.
methodOfResistance
Indicates a way or technique by which resistance is carried out or expressed.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2f09608190bc8e465e53b39e2e |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:35 p.m.