Triple
T10179647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CC0 |
E235951
|
entity |
| Predicate | deedURL |
P92546
|
FINISHED |
| Object | https://creativecommons.org/publicdomain/zero/1.0/ |
—
|
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: https://creativecommons.org/publicdomain/zero/1.0/ | Statement: [CC0, deedURL, https://creativecommons.org/publicdomain/zero/1.0/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deedURL Context triple: [CC0, deedURL, https://creativecommons.org/publicdomain/zero/1.0/]
-
A.
confirmationDocument
Indicates that there exists a document serving as formal confirmation or verification of an action, event, or agreement between entities.
-
B.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
C.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
D.
allegedDeedDate
Indicates the date on which a deed or action is claimed or reported to have occurred, without asserting that it actually took place.
-
E.
documentSignedBy
Indicates that a document has been formally signed or authorized by a specific entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cd7edc6cf081909d95859d880a4059 |
completed | April 1, 2026, 8:23 p.m. |
Created at: March 30, 2026, 9:11 p.m.