Triple
T53942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCP/IP |
E1063
|
entity |
| Predicate | includesProtocol |
P1393
|
FINISHED |
| Object | IP |
—
|
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: IP | Statement: [TCP/IP, includesProtocol, IP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesProtocol Context triple: [TCP/IP, includesProtocol, IP]
-
A.
usesProtocolSuite
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
B.
protocol
Indicates that one entity defines or follows a specific set of rules or procedures governing how it interacts or communicates with another entity.
-
C.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
includesLanguage
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
-
E.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b3a9e848190b80de3c858678b3a |
completed | Feb. 28, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a24ac52fb08190aa7c38f83434f795 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.