Triple

T278450
Position Surface form Disambiguated ID Type / Status
Subject Warrior infantry fighting vehicle E5299 entity
Predicate programmeName P9004 FINISHED
Object Mechanised Infantry Combat Vehicle 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: Mechanised Infantry Combat Vehicle | Statement: [Warrior infantry fighting vehicle, programmeName, Mechanised Infantry Combat Vehicle]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: programmeName
Context triple: [Warrior infantry fighting vehicle, programmeName, Mechanised Infantry Combat Vehicle]
  • A. hasProgramme
    Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
  • B. program
    Indicates that an entity creates, writes, or develops a computer program or software application.
  • C. programType
    Indicates the category or kind of program to which an entity belongs or with which it is associated.
  • D. createdProgram
    Indicates that an entity authored, developed, or produced a particular program (such as software or a coded application).
  • E. hasGlobalProgramme
    Indicates that an entity operates, participates in, or is associated with a programme that is implemented or recognized at a global or international level.
  • 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_69a257e6c8788190987dfe705ca2912a completed Feb. 28, 2026, 2:50 a.m.
NER Named-entity recognition batch_69a25dee7830819087f153769a8496b9 completed Feb. 28, 2026, 3:15 a.m.
PD Predicate disambiguation batch_69a25b765f488190b2cbe4b45cd42821 completed Feb. 28, 2026, 3:05 a.m.
PDg Predicate description generation batch_69a25c4b773c81908f1017f40b0bfd07 completed Feb. 28, 2026, 3:08 a.m.
Created at: Feb. 28, 2026, 2:59 a.m.