Triple
T37123863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HChaCha20 |
E919336
|
entity |
| Predicate | inputComponents |
P58007
|
FINISHED |
| Object | 4 constant words |
—
|
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: 4 constant words | Statement: [HChaCha20, inputComponents, 4 constant words]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputComponents Context triple: [HChaCha20, inputComponents, 4 constant words]
-
A.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
B.
selectionComponents
chosen
Indicates that certain elements function as constituent parts or options within a larger selection or choice.
-
C.
input
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
-
D.
inputProperty
Indicates that one entity serves as an input characteristic, attribute, or parameter that influences or configures another entity or process.
-
E.
inputRole
Indicates that an entity serves as an input or source participant in a process, action, or relationship.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.