Triple
T20978221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proxy Mobile IPv6 |
E516681
|
entity |
| Predicate | mobilityManagementType |
P142334
|
FINISHED |
| Object | network-based mobility management |
—
|
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-based mobility management | Statement: [Proxy Mobile IPv6, mobilityManagementType, network-based mobility management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobilityManagementType Context triple: [Proxy Mobile IPv6, mobilityManagementType, network-based mobility management]
-
A.
mobilityRule
Indicates a rule or constraint governing how an entity is allowed or able to move or change location within a given context.
-
B.
cellReselectionSupport
Indicates whether a network cell is configured to allow and support mobile devices moving their connection (reselecting) from one cell to another.
-
C.
signalingMode
Indicates the method or mechanism by which one entity communicates or transmits signals to another.
-
D.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
-
E.
connectivityMode
Indicates how two or more entities are linked or able to communicate with each other, such as the type or method of connection used between them.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:47 p.m.