Triple
T33027090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SipHash-2-4 |
E845070
|
entity |
| Predicate | prfProperty |
P118612
|
FINISHED |
| Object | designed to behave like a pseudorandom function |
—
|
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: designed to behave like a pseudorandom function | Statement: [SipHash-2-4, prfProperty, designed to behave like a pseudorandom function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prfProperty Context triple: [SipHash-2-4, prfProperty, designed to behave like a pseudorandom function]
-
A.
protocolProperty
Indicates that a specific property or characteristic is defined or governed by a particular protocol.
-
B.
propertiesType
Indicates that one entity is classified as a specific type or category of properties associated with another entity.
-
C.
structureProperty
Indicates that one entity has a structural attribute, feature, or characteristic that describes how it is organized or composed.
-
D.
metaProperty
Indicates that one property functions as a higher-level descriptor or attribute about another property, rather than about an entity directly.
-
E.
artifactProperty
chosen
Indicates that an artifact possesses a specific property, characteristic, or attribute.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:23 a.m.