Triple
T22766630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oh! Susanna |
E563142
|
entity |
| Predicate | inPublicDomain |
P22736
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Oh! Susanna, inPublicDomain, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inPublicDomain Context triple: [Oh! Susanna, inPublicDomain, Yes]
-
A.
inThePublicDomain
Indicates that the subject is not protected by intellectual property rights and may be freely used, copied, or distributed by anyone.
-
B.
isPublicDomain
chosen
Indicates that the subject is not protected by intellectual property rights and can be freely used, copied, and distributed by anyone.
-
C.
reasonForPublicDomainStatus
Indicates the specific legal or factual reason why a work has entered the public domain.
-
D.
readPubliclyIn
Indicates that an entity performs a reading of something (e.g., a text or work) in a public setting or context.
-
E.
ownedPublication
Indicates that one entity possesses ownership or controlling rights over a particular publication.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a80e2688190b76844c408929d32 |
completed | April 29, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:26 p.m.