Triple
T1673600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Gurkha recruiting centers in Nepal |
E36179
|
entity |
| Predicate | processStage |
P4106
|
FINISHED |
| Object | initial 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: initial enlistment | Statement: [British Gurkha recruiting centers in Nepal, processStage, initial enlistment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processStage Context triple: [British Gurkha recruiting centers in Nepal, processStage, initial enlistment]
-
A.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
B.
partOfProcess
chosen
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
C.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
D.
programPhase
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
E.
stages
Indicates that one entity organizes, presents, or sets up another entity (such as an event, performance, or situation) to take place or be displayed.
- 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.