Triple
T33056929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blowfish |
E845867
|
entity |
| Predicate | recommendedForNewSystems |
P177609
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Blowfish, recommendedForNewSystems, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedForNewSystems Context triple: [Blowfish, recommendedForNewSystems, false]
-
A.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
B.
recommendedMode
Indicates that one entity is suggested or advised as the preferred mode, method, or way of doing or experiencing something in relation to another entity.
-
C.
recommendsUseOf
Indicates that one entity advises, endorses, or suggests the use of another entity as appropriate or beneficial in a given context.
-
D.
commendedFor
Indicates that one entity has expressed praise or approval toward another entity specifically because of a particular action, quality, or achievement.
-
E.
recommendedIn
Indicates that one entity is suggested or endorsed within the context, content, or scope of another entity (such as a document, list, or recommendation source).
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:25 a.m.