Triple
T24205485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Individual Training |
E600092
|
entity |
| Predicate | hasTraineeRole |
P41566
|
FINISHED |
| Object | soldier |
—
|
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: soldier | Statement: [Advanced Individual Training, hasTraineeRole, soldier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraineeRole Context triple: [Advanced Individual Training, hasTraineeRole, soldier]
-
A.
hasTrainingRole
chosen
Indicates that an entity holds or is assigned a specific role within a training or instructional context.
-
B.
hasTrainingComplexRole
Indicates that an entity holds a specific role or function within a training complex or training facility.
-
C.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
D.
roleInTrain
Indicates the specific function or position an entity holds within the context of a train (e.g., passenger, conductor, locomotive, or car type).
-
E.
hasFormerPupilRole
Indicates that an entity previously held the role or position of a pupil or student in relation to another entity.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca52cb881908c99913ea93bc88e |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.