Triple
T2122304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Domain Mark |
E43950
|
entity |
| Predicate | nonCommercial |
P24924
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Public Domain Mark, nonCommercial, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonCommercial Context triple: [Public Domain Mark, nonCommercial, false]
-
A.
isNonCommercial
chosen
Indicates that the associated entity, use, or activity is not intended for or involved in commercial, profit-generating purposes.
-
B.
nonExclusive
Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
-
C.
commercial
Indicates that one entity is engaged in a business-related or profit-oriented relationship, activity, or transaction with another entity.
-
D.
nonExample
Indicates that something is explicitly identified as not being an example or instance of a given concept, category, or pattern.
-
E.
nonConstructive
Indicates that the relationship or action does not provide a direct, explicit method or example to realize or build the object, outcome, or proof it asserts exists.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb51e8088190a1aeafee4e8dff63 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.