Triple
T24985785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rus'–Byzantine Wars |
E625302
|
entity |
| Predicate | latestConflict |
P95832
|
FINISHED |
| Object | Rus'–Byzantine War of 1043 |
—
|
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: Rus'–Byzantine War of 1043 | Statement: [Rus'–Byzantine Wars, latestConflict, Rus'–Byzantine War of 1043]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latestConflict Context triple: [Rus'–Byzantine Wars, latestConflict, Rus'–Byzantine War of 1043]
-
A.
latestMajorConflict
chosen
Indicates the most recent significant conflict or war involving the given entity or between the specified entities.
-
B.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
C.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
D.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
E.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490a4a508190bdd6c2dde03e251a |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:03 a.m.