Triple
T13226107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Federal Service for Intellectual Property |
E314883
|
entity |
| Predicate | typeOfIPHandled |
P67337
|
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: [Russian Federal Service for Intellectual Property, typeOfIPHandled, patents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfIPHandled Context triple: [Russian Federal Service for Intellectual Property, typeOfIPHandled, patents]
-
A.
hasIP
Indicates that one entity possesses, is assigned, or is associated with a specific IP address.
-
B.
typeOfProcedureHandled
chosen
Indicates the specific kind or category of procedure that an entity is responsible for managing or processing.
-
C.
usesIP
Indicates that one entity makes use of, operates through, or is associated with a particular IP address.
-
D.
basedOnIP
Indicates that the relationship or action is determined or derived from an entity’s IP address.
-
E.
informationTypeHandled
Indicates that an entity is responsible for processing, managing, or dealing with a particular type or category of information.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d3128348190836158467e9cfbe2 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:19 p.m.