Triple
T4503530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian special forces |
E101276
|
entity |
| Predicate | typicalRecruitment |
P4145
|
FINISHED |
| Object | career military personnel |
—
|
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: career military personnel | Statement: [Russian special forces, typicalRecruitment, career military personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRecruitment Context triple: [Russian special forces, typicalRecruitment, career military personnel]
-
A.
recruitmentBase
Indicates the foundational source, location, or context from which recruitment efforts or recruited entities originate.
-
B.
recruitmentFrom
chosen
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
C.
recruitsFor
Indicates that one entity actively seeks out, enlists, or brings in participants, members, or resources on behalf of another entity, such as an organization, event, or cause.
-
D.
recruitedAs
Indicates that one entity has been brought into a role, position, or organization by another through a recruitment process.
-
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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56fca7d4819081deb34628e04f00 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.