Triple
T2383381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4250 |
E46361
|
entity |
| Predicate | registers |
P3328
|
FINISHED |
| Object | SSH protocol parameters with IANA |
—
|
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: SSH protocol parameters with IANA | Statement: [RFC 4250, registers, SSH protocol parameters with IANA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registers Context triple: [RFC 4250, registers, SSH protocol parameters with IANA]
-
A.
relatedRegister
Indicates a relationship where one entity is associated with, linked to, or corresponds to a particular register or record in a system.
-
B.
generalPurposeRegisters
Indicates that the relationship involves general-purpose registers used to hold data or addresses during computation or instruction execution.
-
C.
register
chosen
Indicates that an entity formally records or enrolls another entity or itself in an official system, list, or record.
-
D.
registerCount
Indicates the number of registers associated with or allocated to a given entity in a system.
-
E.
registrationContext
Indicates the situational or environmental context under which a registration event occurs, such as conditions, purpose, or setting.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7bafa248190a68e8f1e081f4817 |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.