Triple
T18750463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Directive 93/42/EEC |
E458510
|
entity |
| Predicate | OJPagination |
P95961
|
FINISHED |
| Object | page 1–43 |
—
|
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: page 1–43 | Statement: [Council Directive 93/42/EEC, OJPagination, page 1–43]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OJPagination Context triple: [Council Directive 93/42/EEC, OJPagination, page 1–43]
-
A.
E2Page
chosen
Indicates a relationship where an entity is associated with, or corresponds to, a specific page (such as a page in a document, website, or dataset).
-
B.
supportsPagination
Indicates that the subject provides or is compatible with dividing content or results into discrete pages that can be navigated sequentially.
-
C.
pageSize
Indicates the size or amount of content (such as items, records, or data) that is included or displayed on a single page.
-
D.
pageNumber
Indicates the specific numerical position of a page within an ordered sequence of pages.
-
E.
pageIndexNotation
Indicates that a specific notation or label is used to identify the index or position of a page within an ordered sequence of pages.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ec71cc8190bb6d3fa6cca6dc8c |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.