Triple
T32062165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Licensing |
E818773
|
entity |
| Predicate | offeredLicensesFor |
P193727
|
FINISHED |
| Object | AAC implementations |
—
|
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: AAC implementations | Statement: [Via Licensing, offeredLicensesFor, AAC implementations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredLicensesFor Context triple: [Via Licensing, offeredLicensesFor, AAC implementations]
-
A.
offersLicense
Indicates that one entity grants or makes available a license to another entity.
-
B.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
C.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
D.
supportsLicense
Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
-
E.
offersAt
Indicates that one entity makes another entity available under specified terms, such as a particular price, time, or location.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
| PDg | Predicate description generation | batch_69fd509cdc5c8190a5f2c451bc0d0b25 |
completed | May 8, 2026, 2:55 a.m. |
Created at: May 1, 2026, 12:22 a.m.