Triple
T33134446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2244 |
E847960
|
entity |
| Predicate | networkProtocolSuite |
P1215
|
FINISHED |
| Object | Internet Protocol Suite |
—
|
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: Internet Protocol Suite | Statement: [RFC 2244, networkProtocolSuite, Internet Protocol Suite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkProtocolSuite Context triple: [RFC 2244, networkProtocolSuite, Internet Protocol Suite]
-
A.
networkSuite
Indicates that an entity is part of, provided by, or associated with a particular network-related software or service suite.
-
B.
usesProtocolSuite
chosen
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
C.
networkProtocolDomain
Indicates the network protocol or protocol family within which a given communication, service, or interaction operates.
-
D.
networkLayerSupport
Indicates that one entity provides or is compatible with the network-layer functionality or protocols required by another entity.
-
E.
protocolNumberSpace
Indicates that there is a defined set or range of valid protocol numbers associated with the given protocol or system.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:27 a.m.