Triple
T35620909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European intellectual property system |
E1029307
|
entity |
| Predicate | includesRightType |
P96022
|
FINISHED |
| Object | patents |
—
|
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: patents | Statement: [European intellectual property system, includesRightType, patents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRightType Context triple: [European intellectual property system, includesRightType, patents]
-
A.
includesRight
chosen
Indicates that one entity contains, encompasses, or grants a particular right to another entity.
-
B.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
-
C.
includesExpressionType
Indicates that one entity contains or encompasses a specific type or category of expression as part of its definition or structure.
-
D.
includesUniformType
Indicates that one entity contains or encompasses a specific type of uniform within its scope or composition.
-
E.
includesStateType
Indicates that something encompasses or contains a particular type or category of state within it.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.