Triple
T20978089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIH Function |
E516678
|
entity |
| Predicate | supportsMobilityManagementFor |
P64037
|
FINISHED |
| Object | Mobile nodes |
—
|
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: Mobile nodes | Statement: [MIH Function, supportsMobilityManagementFor, Mobile nodes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMobilityManagementFor Context triple: [MIH Function, supportsMobilityManagementFor, Mobile nodes]
-
A.
supportsRoamingWith
Indicates that one entity enables or is compatible with another entity’s ability to operate or be accessed while roaming across different networks or locations.
-
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.
supportsMobilityBetween
Indicates that one entity enables, facilitates, or allows movement or travel between two or more other entities or locations.
-
D.
supportsHandoverWith
chosen
Indicates that one entity is capable of transferring control, responsibility, or an ongoing process to another entity in a coordinated handover.
-
E.
hasStationManagement
Indicates that one entity is responsible for managing, operating, or overseeing the activities and administration of a station associated with 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.