Triple
T23154779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | c2.com |
E578409
|
entity |
| Predicate | webProtocol |
P35980
|
FINISHED |
| Object | HTTP |
—
|
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: HTTP | Statement: [c2.com, webProtocol, HTTP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: webProtocol Context triple: [c2.com, webProtocol, HTTP]
-
A.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
B.
networkProtocolDomain
Indicates the network protocol or protocol family within which a given communication, service, or interaction operates.
-
C.
supportedProtocol
chosen
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
D.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
E.
targetProtocol
Indicates the communication protocol that an action, message, or connection is intended to use or be directed toward.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efca1f081908ff1c34ba25f40c3 |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.