Triple
T18033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet |
E356
|
entity |
| Predicate | usesProtocol |
P203
|
FINISHED |
| Object | TCP |
E1063
|
NE 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: TCP | Statement: [Internet, usesProtocol, TCP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TCP Context triple: [Internet, usesProtocol, TCP]
-
A.
TCP/IP
chosen
TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
-
B.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
C.
TEC
TEC is the commonly used acronym for the Episcopal Church, a mainline Anglican Christian denomination based in the United States.
-
D.
ARPANET
ARPANET was the pioneering packet-switching network developed in the late 1960s that became the technical foundation of the modern Internet.
-
E.
Tymshare
Tymshare was an influential American time-sharing and computer services company active in the 1960s–1980s that helped pioneer remote computing and software services for businesses.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a2465d9038819087f875a5afac9541 |
completed | Feb. 28, 2026, 1:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a248e73c6c8190a83d10709aa3f9c7 |
completed | Feb. 28, 2026, 1:46 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.