Triple
T28409765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 32 supplementary means of interpretation |
E719630
|
entity |
| Predicate | conditionForUse |
P93022
|
FINISHED |
| Object | interpretation under Article 31 leads to a manifestly absurd or unreasonable result |
—
|
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: interpretation under Article 31 leads to a manifestly absurd or unreasonable result | Statement: [Article 32 supplementary means of interpretation, conditionForUse, interpretation under Article 31 leads to a manifestly absurd or unreasonable result]
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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64d7473008190a5c999617fd44044 |
completed | May 2, 2026, 7:16 p.m. |
Created at: April 28, 2026, 1:25 a.m.