Triple
T5627662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Host-to-Host Protocol |
E147757
|
entity |
| Predicate | documentationContext |
P65508
|
FINISHED |
| Object | early ARPANET RFCs |
—
|
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: early ARPANET RFCs | Statement: [Host-to-Host Protocol, documentationContext, early ARPANET RFCs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationContext Context triple: [Host-to-Host Protocol, documentationContext, early ARPANET RFCs]
-
A.
documentationUI
Indicates a relationship where a user interface element is used to present, navigate, or interact with documentation content.
-
B.
documentationSection
Indicates that one entity is a specific section or subdivision within the documentation of another entity.
-
C.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be interpreted.
-
D.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
E.
draftContext
Indicates the situational or background information in which a draft (such as a preliminary version of a document, plan, or message) is created, edited, or evaluated.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02239500c8190ad3035e44c3b0670 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f40df64819089a659ea00a835ef |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:40 p.m.