Triple
T1632240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCP 38 |
E35280
|
entity |
| Predicate | targetLayer |
P3274
|
FINISHED |
| Object | network 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: network layer | Statement: [BCP 38, targetLayer, network layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetLayer Context triple: [BCP 38, targetLayer, network layer]
-
A.
targetArea
Indicates the specific area or region that is the intended focus or destination of an action or effect.
-
B.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
operationalLayer
chosen
Indicates that one entity functions as an operational layer or level through which another entity’s activities, processes, or services are executed or managed.
-
D.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
E.
targetVertical
Indicates that one entity is directed toward, aligned with, or intended for a specific vertical market, domain, or industry segment.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.