Triple
T16893723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ILO Convention No. 100 |
E424241
|
entity |
| Predicate | conventionNumber |
P124901
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [ILO Convention No. 100, conventionNumber, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conventionNumber Context triple: [ILO Convention No. 100, conventionNumber, 100]
-
A.
associatedConvention
Indicates a relationship where something is linked or connected to a particular convention (such as an event, standard, or formal gathering).
-
B.
conventionSigned
Indicates that an entity has formally agreed to and signed a specific convention or treaty.
-
C.
conventionState
Indicates that an entity is in a particular formal status or phase within a convention or agreed procedural framework.
-
D.
conventionFor
Indicates a relationship where something serves as a standard, rule, or customary practice governing how another thing is done, represented, or interpreted.
-
E.
committeeNumber
Indicates the specific numerical identifier assigned to a committee in a given context or system.
- F. None of above. chosen
Provenance (4 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc6b97c8190b18aca477d6ef647 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32e2c07b081908c8fee9f5507bb9e |
completed | April 18, 2026, 7:09 a.m. |
Created at: April 10, 2026, 5:29 a.m.