Triple
T32939975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASV |
E842639
|
entity |
| Predicate | copyrightStatusUS |
P7333
|
FINISHED |
| Object | public domain |
—
|
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: public domain | Statement: [ASV, copyrightStatusUS, public domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: copyrightStatusUS Context triple: [ASV, copyrightStatusUS, public domain]
-
A.
copyrightStatus
chosen
Indicates the legal protection state of a work, specifying whether and how it is covered by copyright.
-
B.
copyrightOffice
Indicates that an entity is associated with, registered at, or handled by a copyright office or authority responsible for managing copyright matters.
-
C.
copyrightModel
Indicates that one entity serves as the copyright or licensing model that governs the use, distribution, or protection of another entity.
-
D.
intellectualPropertyStatus
Indicates the legal condition or protection state of an entity’s intellectual property, such as whether it is patented, copyrighted, trademarked, pending, or unprotected.
-
E.
copyrightCategory
Indicates the classification of an item according to its copyright status or type of copyright protection.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:20 a.m.