Triple
T37123876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HChaCha20 |
E919336
|
entity |
| Predicate | domainSeparation |
P187170
|
FINISHED |
| Object | uses nonce prefix as diversification input |
—
|
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: uses nonce prefix as diversification input | Statement: [HChaCha20, domainSeparation, uses nonce prefix as diversification input]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainSeparation Context triple: [HChaCha20, domainSeparation, uses nonce prefix as diversification input]
-
A.
definedSeparationFrom
Indicates a formally specified distinction or boundary established between one entity and another.
-
B.
knownSeparation
Indicates that a separation or split between entities is recognized or has been established as a known fact.
-
C.
typeOfSeparation
Indicates the specific manner or category of separation that exists or occurred between entities.
-
D.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
-
E.
separationContext
Indicates the situational or contextual factors under which two entities become separated or are considered distinct from one another.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:15 p.m.