Triple
T10341328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Regulation (EC) No 1/2003 |
E243132
|
entity |
| Predicate | reformKnownAs |
P89074
|
FINISHED |
| Object | modernisation of EU antitrust rules |
—
|
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: modernisation of EU antitrust rules | Statement: [Council Regulation (EC) No 1/2003, reformKnownAs, modernisation of EU antitrust rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformKnownAs Context triple: [Council Regulation (EC) No 1/2003, reformKnownAs, modernisation of EU antitrust rules]
-
A.
reformName
Indicates that an entity has undergone a reform or change resulting in a new name or designation.
-
B.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
C.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
-
D.
officialRenaming
Indicates that an entity has been given a new official name, formally replacing its previous designation.
-
E.
afterConversionKnownAs
chosen
Indicates that an entity is referred to by a new name or identifier after undergoing a conversion or transformation.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:55 a.m.