Triple
T18372072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTEA |
E446204
|
entity |
| Predicate | effectOnPublicDomain |
P51744
|
FINISHED |
| Object | postponed expiration of many copyrights |
—
|
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: postponed expiration of many copyrights | Statement: [CTEA, effectOnPublicDomain, postponed expiration of many copyrights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnPublicDomain Context triple: [CTEA, effectOnPublicDomain, postponed expiration of many copyrights]
-
A.
isPublicDomain
Indicates that the subject is not protected by intellectual property rights and can be freely used, copied, and distributed by anyone.
-
B.
affectedDomain
Indicates the domain, field, or area that is impacted or influenced by a given action, event, or condition.
-
C.
reasonForPublicDomainStatus
chosen
Indicates the specific legal or factual reason why a work has entered the public domain.
-
D.
effectOfPublication
Indicates the impact or consequence that a particular publication has on something, such as knowledge, behavior, policy, or subsequent events.
-
E.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
- 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_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. |
Created at: April 10, 2026, 10:44 a.m.