Triple
T33056907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blowfish |
E845867
|
entity |
| Predicate | usesSubkeys |
P193002
|
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: [Blowfish, usesSubkeys, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSubkeys Context triple: [Blowfish, usesSubkeys, true]
-
A.
correspondsToSubkeyUnder
Indicates that one entity matches or is associated with a specific subordinate key nested under another entity.
-
B.
usesSubgroup
Indicates that one entity employs, incorporates, or operates through a specific subgroup of another entity or system.
-
C.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
-
D.
usedWithSubunit
Indicates that one entity is employed, operated, or functions in conjunction with a specific subunit of another entity.
-
E.
usedBySubsidiaryOf
Indicates that something is used by an entity that is a subsidiary of another organization.
- 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_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
| PDg | Predicate description generation | batch_69fd35d029588190a525aa8a506e7708 |
completed | May 8, 2026, 1:01 a.m. |
Created at: May 1, 2026, 1:25 a.m.