Triple
T18372103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 105-298 |
E446205
|
entity |
| Predicate | newTermForCorporateWorks |
P130872
|
FINISHED |
| Object | 95 years from publication |
—
|
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: 95 years from publication | Statement: [Public Law 105-298, newTermForCorporateWorks, 95 years from publication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: newTermForCorporateWorks Context triple: [Public Law 105-298, newTermForCorporateWorks, 95 years from publication]
-
A.
previousCorporateTerm
Indicates that one corporate term or period of office directly preceded another in time.
-
B.
developmentCorporationEstablished
Indicates that a development corporation has been formally created or founded.
-
C.
publicCompany
Indicates that a company is publicly traded, meaning its ownership shares are available to the general public on one or more stock exchanges.
-
D.
createdWork
Indicates that an agent is responsible for bringing a work (such as a creative, intellectual, or produced artifact) into existence.
-
E.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51754539c819083f13b85cacb6cce |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:44 a.m.