Triple
T847155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Labour Recommendations |
E18300
|
entity |
| Predicate | firstAdoptedIn |
P3399
|
FINISHED |
| Object | 1919 |
—
|
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: 1919 | Statement: [International Labour Recommendations, firstAdoptedIn, 1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAdoptedIn Context triple: [International Labour Recommendations, firstAdoptedIn, 1919]
-
A.
officialAdoptionYear
Indicates the year in which something (such as a policy, standard, symbol, or practice) was formally adopted or officially put into use.
-
B.
firstDomesticatedIn
Indicates the place or context where an entity was initially brought under human control or cultivation for the first time.
-
C.
firstAdopters
Indicates that the related entities are among the earliest to adopt, use, or implement a new product, technology, or idea.
-
D.
dateAdopted
chosen
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
-
E.
adoptedAt
Indicates the time or date at which an adoption event took place.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac0ba6b4819089c15ed7e1765502 |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa807adc8190ad808a573cf8e923 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.