Triple
T36671197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EC) No 178/2002 |
E905420
|
entity |
| Predicate | EULawNumber |
P1117
|
FINISHED |
| Object | 178/2002 |
—
|
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: 178/2002 | Statement: [Regulation (EC) No 178/2002, EULawNumber, 178/2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EULawNumber Context triple: [Regulation (EC) No 178/2002, EULawNumber, 178/2002]
-
A.
EURLexSector
Indicates the legal or regulatory sector within the EUR-Lex classification system to which a given document or item is assigned.
-
B.
publicLawNumber
chosen
Indicates the specific public law identifier associated with a legislative act or statute.
-
C.
appliedLawFrom
Indicates that a specific law or legal provision was applied or derived from a particular source, context, or jurisdiction in a legal decision or situation.
-
D.
numberOfLaws
Indicates the quantitative count of laws associated with a given entity or context.
-
E.
legalBasisInEU
Indicates that something (such as a measure, decision, or status) is grounded in, justified by, or derived from a specific legal basis within European Union law.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c79ec578819098ad469098923e29 |
completed | May 3, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.