Triple

T36112541
Position Surface form Disambiguated ID Type / Status
Subject Battle of Gubeikou (Ming–Mongol conflicts) E1044536 entity
Predicate defenseLine P93189 FINISHED
Object Ming Great Wall system 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: Ming Great Wall system | Statement: [Battle of Gubeikou (Ming–Mongol conflicts), defenseLine, Ming Great Wall system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defenseLine
Context triple: [Battle of Gubeikou (Ming–Mongol conflicts), defenseLine, Ming Great Wall system]
  • A. defenseTeam
    Indicates a relationship where one party serves as the legal defense representatives or advocates for another party in a legal or adversarial proceeding.
  • B. usedDefensiveLine chosen
    Indicates that an entity employed or deployed a particular defensive line as part of its strategy or actions.
  • C. defensiveSide
    Indicates which entity is acting in a defensive role or position relative to another entity or situation.
  • D. defensiveStructure
    Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
  • E. primaryDefensiveLine
    Indicates the main line of defense that first engages or protects against an opposing force or threat.
  • 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_69f76e344a4c8190af3858c6d78ba88f completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fb2e940d5c8190bceae77daf4ef512 completed May 6, 2026, 12:05 p.m.
PD Predicate disambiguation batch_69f9fec70bd881909c658a3c5020318b completed May 5, 2026, 2:29 p.m.
Created at: May 3, 2026, 4:08 p.m.