Triple
T28828608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptune |
E727980
|
entity |
| Predicate | preReleaseBuildsLeaked |
P165642
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Neptune, preReleaseBuildsLeaked, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preReleaseBuildsLeaked Context triple: [Neptune, preReleaseBuildsLeaked, yes]
-
A.
hasBuildsFor
Indicates that one entity creates, compiles, or prepares builds specifically intended to run on or support another entity (such as a target platform, environment, or configuration).
-
B.
supportsPreReleaseVersions
Indicates that one entity is capable of handling, accepting, or working with pre-release or non-final versions of another entity.
-
C.
hasBuild
Indicates that one entity has constructed, created, or assembled another entity.
-
D.
publicRelease
Indicates that something is made available to the general public, typically after any private or restricted access period has ended.
-
E.
hasScheduledReleases
Indicates that an entity has one or more releases planned to occur at specific future times.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:37 a.m.