Triple
T21105315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohlsbach |
E520024
|
entity |
| Predicate | licenceCode |
P142863
|
FINISHED |
| Object | OG |
—
|
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: OG | Statement: [Ohlsbach, licenceCode, OG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenceCode Context triple: [Ohlsbach, licenceCode, OG]
-
A.
licenceBuiltIn
Indicates that a licence is inherently included within or comes pre-installed as part of another product, system, or component rather than being added separately.
-
B.
licenseName
Indicates the specific name or title of the license under which an entity is provided or governed.
-
C.
licenseModel
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
-
D.
licenseFocus
Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
-
E.
licenseFamily
Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b6150f08190a3738f1eda7fa834 |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:53 p.m.