Triple
T21998130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IES/ISS Examination |
E543256
|
entity |
| Predicate | recruitmentMode |
P138499
|
FINISHED |
| Object | direct recruitment |
—
|
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: direct recruitment | Statement: [IES/ISS Examination, recruitmentMode, direct recruitment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recruitmentMode Context triple: [IES/ISS Examination, recruitmentMode, direct recruitment]
-
A.
recruitmentMethods
chosen
Indicates the ways or strategies used to attract, source, and enlist individuals for a role, program, or organization.
-
B.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
C.
recruitingFocus
Indicates that an entity’s recruitment efforts are specifically directed toward or concentrated on another entity or group.
-
D.
recruitmentBasis
Indicates the criteria, grounds, or conditions on which an entity is recruited or selected for a role or position.
-
E.
recruitmentBase
Indicates the foundational source, location, or context from which recruitment efforts or recruited entities originate.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276774508190b96870266e10979a |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:19 p.m.