Triple
T3415159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenJDK |
E71990
|
entity |
| Predicate | releaseCadence |
P49318
|
FINISHED |
| Object | approximately every six months |
—
|
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: approximately every six months | Statement: [OpenJDK, releaseCadence, approximately every six months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseCadence Context triple: [OpenJDK, releaseCadence, approximately every six months]
-
A.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
B.
releaseCondition
Indicates the circumstances or requirements under which something is allowed to be released or made available.
-
C.
releaseOfWork
Indicates that one entity makes a work (such as a product, publication, or creative output) publicly available or officially issued.
-
D.
releaseContext
Indicates ending or relinquishing a previously established context or state associated with an interaction or process.
-
E.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb929b8ec8190aef431ec8ea2cf80 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb23d23088190aeafe1379eae2eaa |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:15 p.m.