Triple
T22452750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EC) No 141/2000 |
E555033
|
entity |
| Predicate | marketExclusivityDuration |
P74608
|
FINISHED |
| Object | 10 years |
—
|
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: 10 years | Statement: [Regulation (EC) No 141/2000, marketExclusivityDuration, 10 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketExclusivityDuration Context triple: [Regulation (EC) No 141/2000, marketExclusivityDuration, 10 years]
-
A.
marketExclusivityTerm
chosen
Indicates the duration or conditions under which a product or service is granted exclusive marketing rights, preventing competitors from entering the same market segment.
-
B.
licensingPeriod
Indicates the time span during which a license is valid and its associated rights are legally in effect.
-
C.
existencePeriod
Indicates the time span during which an entity exists or is valid.
-
D.
ownershipPeriod
Indicates the span of time during which an entity holds ownership rights over another entity.
-
E.
hasExclusiveContractFor
Indicates that one party holds sole contractual rights to provide, use, or represent a specific product, service, or opportunity, excluding all other potential counterparties.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4c63e88190aeedc326599edd18 |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.