Triple
T9002530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ips |
E215069
|
entity |
| Predicate | transportLayerConcern |
P11823
|
FINISHED |
| Object | congestion control |
—
|
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: congestion control | Statement: [ips, transportLayerConcern, congestion control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportLayerConcern Context triple: [ips, transportLayerConcern, congestion control]
-
A.
transportLayerFor
Indicates that one entity functions as the transport-layer protocol or mechanism used to carry or deliver another entity’s data.
-
B.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
C.
transportInterface
Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
-
D.
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.
-
E.
transportIsolationCause
Indicates that an entity’s isolation or separation is caused by limitations, disruptions, or barriers in transportation or transit.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6957bd5481908ce74f32f8d197de |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.