Triple
T26409158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GHASH |
E663911
|
entity |
| Predicate | operationOrder |
P113075
|
FINISHED |
| Object | processes input blocks sequentially |
—
|
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: processes input blocks sequentially | Statement: [GHASH, operationOrder, processes input blocks sequentially]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationOrder Context triple: [GHASH, operationOrder, processes input blocks sequentially]
-
A.
operationSequence
chosen
Indicates that one operation occurs in a specific order relative to another within a defined sequence of actions.
-
B.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
-
C.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
D.
orderingType
Indicates the specific method or arrangement by which items, events, or entities are ordered or sequenced relative to one another.
-
E.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 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. |
Created at: April 26, 2026, 11:37 p.m.