Triple
T24985784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rus'–Byzantine Wars |
E625302
|
entity |
| Predicate | earliestConflict |
P92660
|
FINISHED |
| Object | Rus'–Byzantine War of 860 |
—
|
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 860 | Statement: [Rus'–Byzantine Wars, earliestConflict, Rus'–Byzantine War of 860]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestConflict Context triple: [Rus'–Byzantine Wars, earliestConflict, Rus'–Byzantine War of 860]
-
A.
conflictBeganInYear
Indicates that the specified conflict started or first broke out in the given calendar year.
-
B.
startOfMajorConflict
chosen
Indicates that one event marks the beginning or initial outbreak of a major conflict between parties.
-
C.
conflictEra
Indicates that two entities are associated with the same historical period or era of conflict.
-
D.
hasHistoricalPeriodOfConflict
Indicates that there exists a specific historical period during which the related entities were engaged in conflict or hostilities.
-
E.
conflictStartTime
Indicates the specific point in time at which a conflict between entities begins.
- 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_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:03 a.m.