Triple
T4834527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EU) No 1092/2010 |
E108024
|
entity |
| Predicate | OJNumber |
P60313
|
FINISHED |
| Object | 331 |
—
|
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: 331 | Statement: [Regulation (EU) No 1092/2010, OJNumber, 331]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OJNumber Context triple: [Regulation (EU) No 1092/2010, OJNumber, 331]
-
A.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
B.
ISONumber
Indicates that an entity is associated with, identified by, or conforms to a specific ISO (International Organization for Standardization) number or standard.
-
C.
UAXNumber
Indicates a relationship where an entity is associated with a specific UAX (User Access/Authorization/Account/Unit Assignment, etc.) identification number used for tracking or reference.
-
D.
junctionNumber
Indicates the identifying number assigned to a specific junction or intersection within a network or system.
-
E.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
- F. None of above. chosen
Provenance (4 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:25 p.m.