Triple
T8328919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Regulation (EC) No 2157/2001 |
E195026
|
entity |
| Predicate | OJPhrase |
P13561
|
FINISHED |
| Object | OJ L 294 |
—
|
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: OJ L 294 | Statement: [Council Regulation (EC) No 2157/2001, OJPhrase, OJ L 294]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OJPhrase Context triple: [Council Regulation (EC) No 2157/2001, OJPhrase, OJ L 294]
-
A.
meaningOfPhrase
Indicates that one entity expresses or defines the semantic content or interpretation of a given phrase.
-
B.
usedPhrase
chosen
Indicates that one entity employed or expressed a particular phrase in speech, writing, or another form of communication.
-
C.
mainPhrase
Indicates that the referenced phrase functions as the primary or central phrase within a larger linguistic or structural unit.
-
D.
sentenceOf
Indicates that one entity is a sentence that belongs to, is contained in, or is part of another larger text or document.
-
E.
isUsedInPhrase
Indicates that something (such as a word, expression, or symbol) appears as a component within a particular phrase.
- 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.