Triple
T2128380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Youth Labor Army |
E46476
|
entity |
| Predicate | usesPersonnelType |
P11922
|
FINISHED |
| Object | conscripted youth |
—
|
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: conscripted youth | Statement: [Youth Labor Army, usesPersonnelType, conscripted youth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPersonnelType Context triple: [Youth Labor Army, usesPersonnelType, conscripted youth]
-
A.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
B.
appliesToPerson
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific person.
-
C.
usedByPerson
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
-
D.
hasWorkforceType
chosen
Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
-
E.
employmentType
Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb7659f48190871cb27faf47e18a |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.