Triple
T20978234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proxy Mobile IPv6 |
E516681
|
entity |
| Predicate | roleOfMobileAccessGateway |
P110756
|
FINISHED |
| Object | proxy mobility agent on access router |
—
|
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: proxy mobility agent on access router | Statement: [Proxy Mobile IPv6, roleOfMobileAccessGateway, proxy mobility agent on access router]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfMobileAccessGateway Context triple: [Proxy Mobile IPv6, roleOfMobileAccessGateway, proxy mobility agent on access router]
-
A.
roleInGateway
chosen
Indicates that an entity holds a specific function or responsibility within a particular gateway system or process.
-
B.
roleIn3GPP
Indicates that an entity holds a specific role or function within the context of 3GPP (Third Generation Partnership Project) standards or activities.
-
C.
roleOfDevice
Indicates that a device participates in a situation or system with a specified functional role or purpose.
-
D.
architectOfGateway
Indicates that one entity is the architect responsible for designing or creating a specific gateway associated with another entity.
-
E.
servesAsGatewayTo
Indicates that one entity functions as an entry point, access route, or intermediary channel that enables reaching or connecting to another 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba65b0881908bc00981053edb68 |
completed | April 21, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:47 p.m.