Triple

T3554169
Position Surface form Disambiguated ID Type / Status
Subject Battle of Hobkirk’s Hill E75178 entity
Predicate RawdonRank P50567 FINISHED
Object Lord and British commander at Camden 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: Lord and British commander at Camden | Statement: [Battle of Hobkirk’s Hill, RawdonRank, Lord and British commander at Camden]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: RawdonRank
Context triple: [Battle of Hobkirk’s Hill, RawdonRank, Lord and British commander at Camden]
  • A. depthRank
    Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
  • B. capacityRank
    Indicates the relative ordering of entities based on how much capacity (e.g., volume, throughput, or capability) they possess compared to others.
  • C. rankedBy
    Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
  • D. rankedAs
    Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
  • E. SSRank
    Indicates a ranking relationship that orders entities based on their social status, standing, or relative importance within a specified context.
  • F. None of above. chosen

Provenance (4 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_69ad85d33c6c819081d5ac1df13b5680 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc05549d88190acdebdd542ea1a67 completed March 8, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69adb83270ac819083967db0570167d2 completed March 8, 2026, 5:56 p.m.
PDg Predicate description generation batch_69adba25c66c81909a05a97327828c41 completed March 8, 2026, 6:04 p.m.
Created at: March 8, 2026, 3:20 p.m.