Triple
T63748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UDP |
E1266
|
entity |
| Predicate | OSIEquivalentLayer |
P2553
|
FINISHED |
| Object | Layer 4 |
—
|
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: Layer 4 | Statement: [UDP, OSIEquivalentLayer, Layer 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OSIEquivalentLayer Context triple: [UDP, OSIEquivalentLayer, Layer 4]
-
A.
operationalLayer
Indicates that one entity functions as an operational layer or level through which another entity’s activities, processes, or services are executed or managed.
-
B.
operatesOnLayer
chosen
Indicates that an entity performs actions or functions specifically targeting a particular layer within a layered structure or system.
-
C.
oakAffinity
Indicates a special connection, preference, or strong association between an entity and oak (such as oak trees, wood, or oak-related environments).
-
D.
linkLayer
Indicates a relationship where one entity is connected to another at the data link (Layer 2) level of a network stack, enabling direct frame-level communication between them.
-
E.
implementedUnder
Indicates that an action, policy, or process is carried out within the scope, authority, or framework defined by a particular higher-level plan, rule, or governing entity.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea3c44081908fa3856969881d1f |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.