Triple
T8328952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Regulation (EC) No 2157/2001 |
E195026
|
entity |
| Predicate | CELEXNumber |
P65929
|
FINISHED |
| Object | 32001R2157 |
—
|
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: 32001R2157 | Statement: [Council Regulation (EC) No 2157/2001, CELEXNumber, 32001R2157]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CELEXNumber Context triple: [Council Regulation (EC) No 2157/2001, CELEXNumber, 32001R2157]
-
A.
legalCitationNumber
chosen
Indicates the specific identifying number assigned to a legal citation that references a law, case, or legal document.
-
B.
publicLawNumber
Indicates the specific public law identifier associated with a legislative act or statute.
-
C.
legalCitationSystem
Indicates a system or convention used to reference and identify legal authorities such as cases, statutes, or regulations.
-
D.
clauseNumber
Indicates the specific numbered position or identifier assigned to a clause within a larger document or agreement.
-
E.
legalCitation
Indicates that one legal document, case, or authority formally references or cites another as a source of legal support or precedent.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fb812508190aed8a283dacf712e |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.