Triple
T515896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transmission Control Protocol |
E10705
|
entity |
| Predicate | initialPublication |
P15299
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Transmission Control Protocol, initialPublication, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialPublication Context triple: [Transmission Control Protocol, initialPublication, 1974]
-
A.
initialPublicationForm
Indicates the original format or medium in which a work was first published.
-
B.
firstPublisher
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
C.
placeOfFirstPublication
Indicates the location where a work was first published or made publicly available.
-
D.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
E.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1836b688190a60cc901a8724159 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f1137e948190838303cdaa757a5a |
completed | Feb. 28, 2026, 1:43 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.