Triple
T17391424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ILO Convention No. 105 |
E422831
|
entity |
| Predicate | prohibitsUseOfForcedLabourFor |
P272
|
FINISHED |
| Object | Political coercion |
—
|
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: Political coercion | Statement: [ILO Convention No. 105, prohibitsUseOfForcedLabourFor, Political coercion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prohibitsUseOfForcedLabourFor Context triple: [ILO Convention No. 105, prohibitsUseOfForcedLabourFor, Political coercion]
-
A.
usedForcedLabor
Indicates that an entity compelled people to work against their will, typically under coercion, threat, or without fair compensation.
-
B.
labourOf
Indicates that one entity is the work, effort, or labor performed or contributed by another entity.
-
C.
laborProvision
Indicates the provision or supply of labor or workforce from one party to another for work or services.
-
D.
prohibits
chosen
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
E.
workProhibited
Indicates that an entity is not allowed or is forbidden to perform a particular work or job activity.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43aba5398819096846bdeefde0788 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.