Triple

T9035776
Position Surface form Disambiguated ID Type / Status
Subject Battle of Campus Ergenus E216488 entity
Predicate hasChronologicalOrderWithinConflict P26528 FINISHED
Object early 4th-century engagement 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: early 4th-century engagement | Statement: [Battle of Campus Ergenus, hasChronologicalOrderWithinConflict, early 4th-century engagement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasChronologicalOrderWithinConflict
Context triple: [Battle of Campus Ergenus, hasChronologicalOrderWithinConflict, early 4th-century engagement]
  • A. hasOngoingConflict
    Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
  • B. framesConflictAs
    Indicates that one entity presents or interprets a situation, issue, or interaction specifically in terms of conflict or opposition between parties.
  • C. chronologyWithinConflict chosen
    Indicates that one event or time period occurs within the temporal span of a specified conflict or war.
  • D. previousConflict
    Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
  • E. chronologicallyAfter
    Indicates that one event or state occurs later in time than another.
  • 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_69ca83d10b608190b2b2f8e0a7faaf14 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc6ac0b00c8190a7250b86bb7cc276 completed April 1, 2026, 12:45 a.m.
PD Predicate disambiguation batch_69cc5ee3597c81908919cf866ae95c24 completed March 31, 2026, 11:55 p.m.
Created at: March 30, 2026, 7:08 p.m.