Triple
T31080359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIND |
E792079
|
entity |
| Predicate | notableVersionSeries |
P207345
|
FINISHED |
| Object | BIND 4 |
—
|
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: BIND 4 | Statement: [BIND, notableVersionSeries, BIND 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVersionSeries Context triple: [BIND, notableVersionSeries, BIND 4]
-
A.
notableVersionType
Indicates that one version of an entity is recognized as particularly significant or noteworthy relative to other versions.
-
B.
notableVersionFeatures
Indicates that a particular version of something is associated with specific noteworthy features or characteristics.
-
C.
notableStandardSeries
Indicates that one entity is a standard or benchmark series for which the other entity is notably recognized or associated.
-
D.
notableReleaseLabel
Indicates that a creative work (such as an album, single, or other release) was issued or published under a particular record label that is especially notable for that release.
-
E.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:02 p.m.