Triple
T20917354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Definition 1.1 |
E515106
|
entity |
| Predicate | hasLicenseCriteria |
P141668
|
FINISHED |
| Object | free redistribution |
—
|
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: free redistribution | Statement: [Open Definition 1.1, hasLicenseCriteria, free redistribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLicenseCriteria Context triple: [Open Definition 1.1, hasLicenseCriteria, free redistribution]
-
A.
hasLicense
Indicates that an entity possesses a valid authorization or permit, typically granted by an authority, to perform a specific activity or use something.
-
B.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
C.
supportsLicense
Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
-
D.
requiresLicenseOf
Indicates that one entity must obtain or hold the license associated with another entity in order to use, access, or perform something.
-
E.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6ec635f4881909a560fb891100d8c |
completed | April 21, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:48 p.m.