Triple
T29504439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patent Act of 1790 |
E748470
|
entity |
| Predicate | requiredStandard |
P39303
|
FINISHED |
| Object | sufficiently useful and important |
—
|
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: sufficiently useful and important | Statement: [Patent Act of 1790, requiredStandard, sufficiently useful and important]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredStandard Context triple: [Patent Act of 1790, requiredStandard, sufficiently useful and important]
-
A.
requiresQualificationStandard
Indicates that performing or engaging in the referenced activity, role, or process is contingent upon meeting a specified qualification standard.
-
B.
establishedRequirement
chosen
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
C.
coreStandard
Indicates that something conforms to, is defined by, or is governed by a central or foundational standard or specification.
-
D.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
E.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
- 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_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 28, 2026, 4:26 p.m.