Triple
T26015945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4833 |
E647021
|
entity |
| Predicate | abbreviationOfProtocol |
P36183
|
FINISHED |
| Object | DHCP |
—
|
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: DHCP | Statement: [RFC 4833, abbreviationOfProtocol, DHCP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbreviationOfProtocol Context triple: [RFC 4833, abbreviationOfProtocol, DHCP]
-
A.
abbreviationOrShortForm
Indicates that one term is an abbreviation or shortened form of another term.
-
B.
abbreviationUsedFor
chosen
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
-
C.
abbreviationUsedBy
Indicates that a particular abbreviation is employed or adopted by a specified entity in its communication, documentation, or usage.
-
D.
abreviaturaFrecuente
Indicates that one term is a common or frequently used abbreviation of another term.
-
E.
abbreviationScheme
Indicates that one entity specifies or uses a particular system or convention for forming abbreviations of another entity.
- 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_69f605b99f9c819088e3a15a2f69dc15 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:03 a.m.