Triple

T1673622
Position Surface form Disambiguated ID Type / Status
Subject British Gurkha recruiting centers in Nepal E36179 entity
Predicate recruitmentType P5414 FINISHED
Object voluntary enlistment 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: voluntary enlistment | Statement: [British Gurkha recruiting centers in Nepal, recruitmentType, voluntary enlistment]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recruitmentType
Context triple: [British Gurkha recruiting centers in Nepal, recruitmentType, voluntary enlistment]
  • A. employmentType
    Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
  • B. recruitmentFrom
    Indicates that one entity recruits or sources members, employees, or participants from another entity.
  • C. recruitmentBasis chosen
    Indicates the criteria, grounds, or conditions on which an entity is recruited or selected for a role or position.
  • D. recruitmentBase
    Indicates the foundational source, location, or context from which recruitment efforts or recruited entities originate.
  • E. recruitingScope
    Indicates the extent or boundaries within which recruiting activities are conducted or targeted.
  • 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_69a8861286808190939afff3ce8ee31e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69ab272a653481908f48aa1eed5de8a4 completed March 6, 2026, 7:12 p.m.
PD Predicate disambiguation batch_69aa61b2f6288190b2348ef7d7e4672d completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:29 p.m.