Triple
T1632225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCP 38 |
E35280
|
entity |
| Predicate | securityDomain |
P3815
|
FINISHED |
| Object | Internet routing security |
—
|
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: Internet routing security | Statement: [BCP 38, securityDomain, Internet routing security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityDomain Context triple: [BCP 38, securityDomain, Internet routing security]
-
A.
securityRole
Indicates that an entity holds a specific security-related role, permission level, or access profile within a system or context.
-
B.
securityService
Indicates a relationship where an entity provides or is responsible for protective, safeguarding, or defense-related services for another entity or system.
-
C.
securityAspect
chosen
Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
-
D.
securityContext
Indicates the security-related settings or constraints under which an action, process, or interaction is performed.
-
E.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
- 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.