Triple
T10179661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CC0 |
E235951
|
entity |
| Predicate | commercialUseAllowed |
P20683
|
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: [CC0, commercialUseAllowed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialUseAllowed Context triple: [CC0, commercialUseAllowed, yes]
-
A.
isNonCommercial
Indicates that the associated entity, use, or activity is not intended for or involved in commercial, profit-generating purposes.
-
B.
commercialAccess
chosen
Indicates that an entity is permitted to use or access something for commercial or profit-generating purposes.
-
C.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
D.
commercialProduct
Indicates that one entity is a product or service offered for sale or commercial use by another entity.
-
E.
commercialPolicy
Indicates that there is a defined set of commercial terms, rules, or conditions governing transactions or business interactions between the related entities.
- 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdecd7ed608190bfdec8b61cc99205 |
completed | April 2, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:11 p.m.