Triple
T33268379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REACH Regulation (EC) No 1907/2006 |
E851711
|
entity |
| Predicate | EUNumber |
P148083
|
FINISHED |
| Object | 1907/2006 |
—
|
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: 1907/2006 | Statement: [REACH Regulation (EC) No 1907/2006, EUNumber, 1907/2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EUNumber Context triple: [REACH Regulation (EC) No 1907/2006, EUNumber, 1907/2006]
-
A.
UNSNumber
Indicates that an entity is associated with a specific United Nations (UN) number used to identify hazardous substances or dangerous goods.
-
B.
EIPNumber
Indicates that an entity is associated with a specific Ethereum Improvement Proposal (EIP) identifier number.
-
C.
celexNumber
chosen
Indicates the official CELEX identifier assigned to a legal act or document within the EU legal database.
-
D.
ISONumber
Indicates that an entity is associated with, identified by, or conforms to a specific ISO (International Organization for Standardization) number or standard.
-
E.
EUAccession
Indicates that an entity becomes a member state of the European Union through the formal accession process.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:32 a.m.