Triple
T20339536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Patent 2,292,387 |
E495701
|
entity |
| Predicate | citedAsPriorArtIn |
P41971
|
FINISHED |
| Object | later spread-spectrum 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: later spread-spectrum patents | Statement: [U.S. Patent 2,292,387, citedAsPriorArtIn, later spread-spectrum patents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citedAsPriorArtIn Context triple: [U.S. Patent 2,292,387, citedAsPriorArtIn, later spread-spectrum patents]
-
A.
subsequentCitationIn
Indicates that one work cites or references another work that appears later in a specified source or sequence.
-
B.
citationOf
Indicates that one entity cites, references, or formally acknowledges another entity as a source.
-
C.
isCitedFor
chosen
Indicates that one entity references another as a source of information, evidence, or authority for a specific claim, idea, or contribution.
-
D.
subsequentCitationBy
Indicates that one work is cited by another work that was produced or published at a later time.
-
E.
citesAs
Indicates that one entity references or acknowledges another as a source of information, authority, or evidence.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678342a0081908ede8006eb5506a3 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:23 a.m.