Triple

T4871427
Position Surface form Disambiguated ID Type / Status
Subject Knights Templar E109091 entity
Predicate battleReputation P24407 FINISHED
Object highly disciplined 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: highly disciplined | Statement: [Knights Templar, battleReputation, highly disciplined]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: battleReputation
Context triple: [Knights Templar, battleReputation, highly disciplined]
  • A. tacticalReputation
    Indicates the perceived level of skill, reliability, or effectiveness an entity has in planning and executing tactics within a given context.
  • B. militaryReputation chosen
    Indicates the perceived standing or esteem of an entity based on its past or present military performance, conduct, or capabilities.
  • C. championshipReputation
    Indicates the recognized status or esteem an entity holds based on its history of success or performance in championships or major competitive titles.
  • D. mythicReputation
    Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
  • E. laterReputation
    Indicates that an entity’s reputation or status at a later time is being referred to in relation to an earlier point or context.
  • 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_69bd440d96a48190b0c87069adef2af1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ff981fc819080d4466c6fe06cf3 completed March 20, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69bd6c28e56081908ee411ac94c3769e completed March 20, 2026, 3:47 p.m.
Created at: March 20, 2026, 1:27 p.m.