Triple
T4340001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces of Oman |
E97555
|
entity |
| Predicate | manpowerSource |
P51517
|
FINISHED |
| Object | volunteer 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: volunteer military service | Statement: [Armed Forces of Oman, manpowerSource, volunteer military service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manpowerSource Context triple: [Armed Forces of Oman, manpowerSource, volunteer military service]
-
A.
personnelSource
chosen
Indicates the origin or provider from which personnel are obtained or assigned.
-
B.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
-
C.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
D.
employerIn
Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
-
E.
associatedWithWorkforce
Indicates a relationship in which an entity is connected or related to a particular workforce, such as its members, activities, or management.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3516f92588190bdf004d8020c1203 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.