Triple
T873156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janissaries |
E18858
|
entity |
| Predicate | recruitmentSystem |
P5414
|
FINISHED |
| Object | devshirme |
—
|
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: devshirme | Statement: [Janissaries, recruitmentSystem, devshirme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recruitmentSystem Context triple: [Janissaries, recruitmentSystem, devshirme]
-
A.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
B.
recruitmentBase
Indicates the foundational source, location, or context from which recruitment efforts or recruited entities originate.
-
C.
recruitmentBasis
chosen
Indicates the criteria, grounds, or conditions on which an entity is recruited or selected for a role or position.
-
D.
recruitmentControlledBy
Indicates that the process of recruiting or selecting members for a group, role, or organization is directed, managed, or determined by a particular controlling entity.
-
E.
recruitmentPolicy
Indicates the rules, criteria, and procedures an organization follows when attracting, selecting, and hiring candidates.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac97d0f88190b67fcb7fc058e4b9 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8b9b5c81909ac71904f8b8b5cd |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.