Triple
T28653950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guinean Armed Forces |
E725276
|
entity |
| Predicate | hasRecruitment |
P51087
|
FINISHED |
| Object | voluntary military service |
—
|
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: voluntary military service | Statement: [Guinean Armed Forces, hasRecruitment, voluntary military service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecruitment Context triple: [Guinean Armed Forces, hasRecruitment, voluntary military service]
-
A.
hasRecruitmentProgram
Indicates that an entity runs or participates in an organized effort to attract, select, and bring in new members, employees, or participants.
-
B.
hasRecruitStatus
Indicates that an entity holds a particular recruitment-related status or stage within a recruiting process.
-
C.
canBeRecruitedFrom
Indicates that one entity is eligible to be recruited, obtained, or enlisted starting from or via another specified entity or source.
-
D.
hasRecruitType
chosen
Indicates that an entity is associated with a specific type or category of recruitment.
-
E.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: April 28, 2026, 4:54 a.m.