Triple
T31080961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLAKE2b |
E792091
|
entity |
| Predicate | usesInternalStructure |
P35482
|
FINISHED |
| Object | HAIFA-like mode |
—
|
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: HAIFA-like mode | Statement: [BLAKE2b, usesInternalStructure, HAIFA-like mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInternalStructure Context triple: [BLAKE2b, usesInternalStructure, HAIFA-like mode]
-
A.
internalStructure
Indicates that one entity is a component, part, or substructure contained within the overall structure of another entity.
-
B.
usedStructure
chosen
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
C.
hasInternal
Indicates that one entity contains another entity within its internal structure or boundaries.
-
D.
usedInStructure
Indicates that something (such as a material, component, or element) is employed as part of the composition or construction of a larger structure.
-
E.
isWithinStructure
Indicates that one entity is located inside the physical or logical boundaries of another structure.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:02 p.m.