Triple
T30720398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacTCP |
E782140
|
entity |
| Predicate | networkStackLayer |
P11823
|
FINISHED |
| Object | transport layer |
—
|
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: transport layer | Statement: [MacTCP, networkStackLayer, transport layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkStackLayer Context triple: [MacTCP, networkStackLayer, transport layer]
-
A.
networkStack
Indicates a relationship where one component or layer is part of, or operates within, a structured hierarchy of networking layers (a network stack) to enable communication.
-
B.
networkStackOrigin
Indicates the original source or layer within a network stack from which a given connection, packet, or network-related event originates.
-
C.
networkLayerIndependence
Indicates that the relationship or action remains valid and unaffected regardless of the underlying network layer or transport mechanism used.
-
D.
networkSuite
Indicates that an entity is part of, provided by, or associated with a particular network-related software or service suite.
-
E.
protocolLayer
chosen
Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:36 p.m.