Triple
T26015944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4833 |
E647021
|
entity |
| Predicate | specifiesProtocolOptionFor |
P80538
|
FINISHED |
| Object | Dynamic Host Configuration Protocol |
—
|
NE NERFINISHED |
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: Dynamic Host Configuration Protocol | Statement: [RFC 4833, specifiesProtocolOptionFor, Dynamic Host Configuration Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesProtocolOptionFor Context triple: [RFC 4833, specifiesProtocolOptionFor, Dynamic Host Configuration Protocol]
-
A.
specifiesProtocol
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
B.
specifiesProtocolExtensionFor
Indicates that one protocol extension defines or constrains the behavior, capabilities, or usage of another protocol.
-
C.
specifiesProtocolVersion
Indicates that an entity defines or sets the particular protocol version to be used in a communication or interaction.
-
D.
protocolOptionCode
chosen
Indicates the specific code that identifies which protocol option is selected or applied in a given context.
-
E.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 22, 2026, 9:03 a.m.