Triple
T8867339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel Blatchford |
E211050
|
entity |
| Predicate | notableDecisionArea |
P85097
|
FINISHED |
| Object | patent infringement cases |
—
|
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: patent infringement cases | Statement: [Samuel Blatchford, notableDecisionArea, patent infringement cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDecisionArea Context triple: [Samuel Blatchford, notableDecisionArea, patent infringement cases]
-
A.
decisionsTakenBy
Indicates that one or more decisions are made or taken by a specified agent or entity.
-
B.
notableResolution
Indicates that an entity is distinguished or recognized for having a particularly important, impactful, or well-known resolution or decision.
-
C.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
D.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
E.
hasNotableDecision
Indicates that an entity is associated with a specific decision that is considered significant or noteworthy in some context.
- 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6108530c819084559f4de669ce20 |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cffe8ec819084c12770fe0578f2 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:51 p.m.