Triple
T3425875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse Temurin |
E72227
|
entity |
| Predicate | supportsLTSReleases |
P25605
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eclipse Temurin, supportsLTSReleases, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLTSReleases Context triple: [Eclipse Temurin, supportsLTSReleases, true]
-
A.
hasLTSReleases
chosen
Indicates that an entity provides or is associated with one or more Long-Term Support (LTS) releases.
-
B.
supportsPreReleaseVersions
Indicates that one entity is capable of handling, accepting, or working with pre-release or non-final versions of another entity.
-
C.
endOfExtendedSupport
Indicates the point in time when extended support for something (such as a product or service) is officially terminated.
-
D.
stableReleasesMaintainedBy
Indicates that the stable (non-development) releases of a software project are currently being maintained or supported by a particular entity.
-
E.
supportsLicense
Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
- F. None of above.
Provenance (3 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9812a648190ac919e7291744b5a |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.