Triple
T9231368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Comment No. 2 on the implementation of article 2 of the Convention |
E221822
|
entity |
| Predicate | legalStatus |
P64
|
FINISHED |
| Object | authoritative but not legally binding in the same way as the Convention text |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: authoritative but not legally binding in the same way as the Convention text | Statement: [General Comment No. 2 on the implementation of article 2 of the Convention, legalStatus, authoritative but not legally binding in the same way as the Convention text]
Provenance (2 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee190204819096b38270a0abc116 |
completed | April 1, 2026, 10:06 a.m. |
Created at: March 30, 2026, 7:29 p.m.