Triple

T3330239
Position Surface form Disambiguated ID Type / Status
Subject Battle of Carchemish E70014 entity
Predicate opposingForceStructure P4567 FINISHED
Object Egyptian army under Pharaoh Necho II with Assyrian remnants 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: Egyptian army under Pharaoh Necho II with Assyrian remnants | Statement: [Battle of Carchemish, opposingForceStructure, Egyptian army under Pharaoh Necho II with Assyrian remnants]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: opposingForceStructure
Context triple: [Battle of Carchemish, opposingForceStructure, Egyptian army under Pharaoh Necho II with Assyrian remnants]
  • A. opposingForce chosen
    Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
  • B. opposingAlliance
    Indicates that two entities belong to rival or mutually opposed alliances or factions.
  • C. offensiveForce
    Indicates the use or application of aggressive or attacking power or violence by one entity against another.
  • D. opposingForcesStatus
    Indicates the current state or condition of two or more forces that are in conflict or opposition to each other.
  • E. besiegingForce
    Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
  • 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_69ad85a24f208190bcf83131bfed3521 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb171ee0881908642504ab0ac8329 completed March 8, 2026, 5:27 p.m.
PD Predicate disambiguation batch_69ada42a19348190a3862ce02451f4aa completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:12 p.m.