Triple
T29504440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patent Act of 1790 |
E748470
|
entity |
| Predicate | requiredDisclosure |
P80428
|
FINISHED |
| Object | specification of the invention |
—
|
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: specification of the invention | Statement: [Patent Act of 1790, requiredDisclosure, specification of the invention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredDisclosure Context triple: [Patent Act of 1790, requiredDisclosure, specification of the invention]
-
A.
requiresSourceDisclosure
Indicates that performing or using something is contingent on revealing or making known the origin or source from which it was derived.
-
B.
typeOfDisclosure
Indicates the specific category or nature of a disclosure made in a given context (e.g., legal, financial, personal).
-
C.
requiredToProvide
chosen
Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
-
D.
coversDisclosureOf
Indicates that one entity’s scope, terms, or provisions include and apply to the act or content of another entity’s disclosure.
-
E.
requiresAdHocDisclosure
Indicates that a situation or transaction necessitates a special, non-routine disclosure beyond standard or regular reporting requirements.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 28, 2026, 4:26 p.m.